Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clone transferProgress is wrong #1941

Open
TalexDreamSoul opened this issue Oct 10, 2022 · 1 comment
Open

Clone transferProgress is wrong #1941

TalexDreamSoul opened this issue Oct 10, 2022 · 1 comment

Comments

@TalexDreamSoul
Copy link

System information

  • node version: v16.17.0
  • npm or yarn version: 8.14.0
  • OS/version/architecture: Windows11 22H2
  • Applicable nodegit version: 0.27.0

When I use like

const repo = await Git.Clone(url, path, {
      fetchOpts: {
        callbacks: {
          transferProgress: (p) => {

            console.log({
               receivedBytes: p.receivedBytes(),
               receivedObjects: p.receivedObjects(),
               totalDeltas: p.totalDeltas(),
               totalObjects: p.totalObjects(),
               indexedDeltas: p.indexedDeltas(),
               indexedObjects: p.indexedObjects(),
               localObjects: p.localObjects()
            });
            
          }
        }
      }
    })
    

I get something wrong that only part of them works. Apart from that, the totalObject is not equals to receivedObjects.
Is that I described is a feature? I WANT some urgent help. For thanks!!!

( Maybe I do not understand the work of git exactly yet. And my english is not pretty good, any problems, correct me please!! )

@TalexDreamSoul
Copy link
Author

When I saw issue#1732, understanding that the total percentage need self count, but why the params is not correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant