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

pin add needs a progress bar #3624

Closed
whyrusleeping opened this issue Jan 22, 2017 · 5 comments
Closed

pin add needs a progress bar #3624

whyrusleeping opened this issue Jan 22, 2017 · 5 comments
Assignees
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Milestone

Comments

@whyrusleeping
Copy link
Member

It currently just prints nothing until its done, this can lead people (myself included) into thinking that its frozen.

@whyrusleeping whyrusleeping added kind/enhancement A net-new feature or improvement to an existing feature help wanted Seeking public contribution on this issue labels Jan 22, 2017
@Voker57
Copy link
Contributor

Voker57 commented Feb 4, 2017

Problem is, it's most likely doing FetchGraph, and it's impossible to tell when it stops until it's done. Show number of fetched nodes/bytes?

@whyrusleeping
Copy link
Member Author

Yeah, thats most of the reason why we don't have a progress bar for this yet. We could do something cool with passing the progress updater down inside a context, and then in the FetchGraph code updating our 'nodes to fetch' and 'nodes fetched' counts as we explore the graph.

@kevina
Copy link
Contributor

kevina commented Feb 8, 2017

I think we need a general framework for somehow showing progress on operations that take a long time. I think the garbage collector falls in the same category. Just some sort of way to indicate progress to the user...

@whyrusleeping
Copy link
Member Author

As @Voker57 said, I think an output of "Fetched/Processed %d nodes" would be sufficient.

Right now i track pin progress by watching ipfs bitswap stat to see the number of received blocks.

As i mentioned in my previous comment, the easiest way to do this would probably be to pass a "Progress Counter" object through the context, and in FetchGraph check if our context has one of these, and update it with information as we fetch things.

@whyrusleeping whyrusleeping added this to the ipfs 0.4.6 milestone Feb 9, 2017
@kevina kevina self-assigned this Feb 9, 2017
@kevina
Copy link
Contributor

kevina commented Feb 9, 2017

Okay, I will look into it and see what I can do.

@kevina kevina added status/in-progress In progress and removed help wanted Seeking public contribution on this issue labels Feb 10, 2017
@whyrusleeping whyrusleeping modified the milestones: Ipfs 0.4.7, ipfs 0.4.6 Feb 16, 2017
@kevina kevina added status/in-progress In progress and removed status/in-progress In progress labels Feb 21, 2017
@whyrusleeping whyrusleeping removed the status/in-progress In progress label Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants