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

Progress Monitoring #2054

Open
gabrielrsep opened this issue Oct 15, 2022 · 3 comments
Open

Progress Monitoring #2054

gabrielrsep opened this issue Oct 15, 2022 · 3 comments
Labels
effort/days Estimated to take multiple days, but less than a week need/analysis Needs further analysis before proceeding P2 Medium: Good to have, but can wait until someone steps up

Comments

@gabrielrsep
Copy link

gabrielrsep commented Oct 15, 2022

I think the app needs a way to monitor the progress of the files being pinned and the garbage collector.

@gabrielrsep gabrielrsep added the need/triage Needs initial labeling and prioritization label Oct 15, 2022
@gabrielrsep gabrielrsep changed the title progress Progress Monitoring Oct 15, 2022
@ipfs ipfs deleted a comment from welcome bot Oct 17, 2022
@SgtPooki
Copy link
Member

SgtPooki commented Oct 17, 2022

@SrStick we have a new feature that will be coming out in the next release, brought over by #1919. We will be pushing out another release this week that will include this change. Does that solve the request you're making here?

Also, there is a chance we could implement a new page where users can view pending actions: file import, pinning files, bitswap wantlist, etc.. (somewhat related to the status update popup at #2030)

We will move this to webui to expand on this

@lidel lidel transferred this issue from ipfs/ipfs-desktop Oct 17, 2022
@ipfs ipfs deleted a comment from welcome bot Oct 17, 2022
@SgtPooki SgtPooki added P2 Medium: Good to have, but can wait until someone steps up need/analysis Needs further analysis before proceeding effort/days Estimated to take multiple days, but less than a week and removed need/triage Needs initial labeling and prioritization labels Oct 17, 2022
@SgtPooki SgtPooki moved this from To do to UX design needed in IPFS-GUI (PL EngRes) Oct 17, 2022
@SgtPooki SgtPooki moved this from UX design needed to Planning in IPFS-GUI (PL EngRes) Oct 17, 2022
@SgtPooki
Copy link
Member

@juliaxbow we still need to work on defining requirements and functionality, but this could use your eyes and input :)

@SgtPooki SgtPooki moved this from Planning to Needs Prep work / blocked in IPFS-GUI (PL EngRes) Nov 22, 2022
@MicahZoltu
Copy link

This is a pretty huge hurdle for new users. I have people who I encourage to use IPFS Desktop, and then when I send them a file hash and they add it to their IPFS desktop the expectation is that it will download in the background. However, there is no UI that indicates whether download is occurring or not, and if you pin it there is also no indication of any sort of progress. For very tiny files that are readily available at major gateways this isn't a big problem, but when I add a file to my local gateway and then share the hash, this file may take hours before it is available to them (especially if it is large).

The net result is everyone who I convince to use IPFS Desktop ends up incredibly confused and can't figure out how to actually access the file I want to share with them. A big part of this is the total lack of feedback on what is actually happening behind the scenes when you add a file to IPFS Desktop by hash.

I looked through the issues in this repository and there are a bunch of places where people talk of adding progress bars and the issues are closed as fixed, but I don't see any progress bars nor anything even indicating that a file is being fetched at all. From the sound of it, adding a file to IPFS Desktop doesn't actually do anything unless you pin it? And if you pin it there is no indication of whether the download of that file to the local client is complete or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/days Estimated to take multiple days, but less than a week need/analysis Needs further analysis before proceeding P2 Medium: Good to have, but can wait until someone steps up
Projects
No open projects
Status: Needs Prep Work / Blocked
Development

No branches or pull requests

3 participants