You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If ipfs pin add is unable to find a chunk, it just sits indefinitely waiting for it.
Just sitting at "Fetched/Processed 8353 nodes" leaves the user with a mystery of what's happening.
I've never seen IPFS want more than 10 or 15 chunks at a time, so there must be a limit on number of lines needed.
Docker does something similar in breaking container images intro chunks... maybe this UI could use some improvement? Here's an example:
obviously showing every CID isn't realistic, but showing the CID's that are in an active "want" state would be a great way to show activity.
The user is already asking for "verbose" information on what's happening via --progress, it feels like IPFS could be providing a lot more information on what it's doing. (searching, downloading, etc)
The text was updated successfully, but these errors were encountered:
when you provide --progress to
ipfs pin add
, you get the following updates:If
ipfs pin add
is unable to find a chunk, it just sits indefinitely waiting for it.Just sitting at "Fetched/Processed 8353 nodes" leaves the user with a mystery of what's happening.
I've never seen IPFS want more than 10 or 15 chunks at a time, so there must be a limit on number of lines needed.
Docker does something similar in breaking container images intro chunks... maybe this UI could use some improvement? Here's an example:
obviously showing every CID isn't realistic, but showing the CID's that are in an active "want" state would be a great way to show activity.
The user is already asking for "verbose" information on what's happening via
--progress
, it feels like IPFS could be providing a lot more information on what it's doing. (searching, downloading, etc)The text was updated successfully, but these errors were encountered: