Wildly inconsistent ETA for uploading
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
The ETA for uploading seems incredibly unreliable.
In the morning the GUI was displaying ~14 hours remaining, while the CLI was displaying ~40 hours with 28+ GB left to upload. I brushed it off and just assumed the CLI was more accurate and I waited a few more hours towards the noon.
When I checked it again, the number barely changed and I still have 25+ GB left to upload. But then a few minutes later, the upload process suddenly halted and seemingly completed without any errors. I cannot tell if the ETA is simply being unreliable or if the client did not correctly upload the files.
I might try to re-download it and check its integrity later on, but it's gonna be real tedious since I don't have much space left in my local drive.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the GUI and CLI upload paths described in the report, focusing on how each calculates and updates the remaining ETA. Reproduce an upload with a large amount of data and compare progress with the completed file set. Done means the ETA is consistent enough to be useful and completion does not occur before the files are verified as uploaded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100