cancelled downloads are marked incorrectly on the Recent Uploads/Downloads page #1173
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1173
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I cancelled a download in progress, and its completeness went to 100% and its state stayed at "fetching segment 1886". This is wrong--if anything its completeness should have stayed at the incomplete percentage that it already was and its state should have changed to "cancelled".
I'm tagging this one with the
regression
tag, partially because I wonder if we shouldn't delay the Tahoe-LAFS v1.8.0 release to address this one as well as perhaps #1166, #1169, #1171 and (maybe, if there is anything to it) #1170.Attachment Tahoe-LAFS - Current Uploads_Downloads.html (2403 bytes) added
I'm about to attach one that ended because I had asked curl to download only a certain range and it had finished doing so, and it is marked as "idle".
Attachment ended-idle-Tahoe-LAFS - Current Uploads_Downloads.html (1104 bytes) added
Hm, weird. The stuck-at-"fetching segment 1886" is definitely a bug. I'm uncertain about the "completeness=100%" part.. what ought that to say when a download is cancelled? Hm, maybe "cancelled" ?
Some of this needs some reworking.. there's a method that is expected to return a number from 0 to 1 that is used to populate the "completed percentage" field. To replace that with a "cancelled" string, we need to get rid of that method, or allow it to return None, or something.
It sounds like these bugs are unimportant enough to leave them in v1.8.0 final. If you agree, please bump them to the "soon" Milestone and remove the "regression" tag.
Oh, if someone could do it real quick, we could fix this bug in v1.8.1. That would be nice!
I couldn't reproduce either of these issues on a fresh checkout of trunk.
When I cancel a download (either by stopping it, if I've downloaded it after using Firefox to access the WUI, or by stopping the curl process, if I've used curl, though I don't see why there should be a difference between the two), I see "Failed (output stopped)" as its status on the status page, and its completeness percentage reflects the amount of data that it had downloaded when I stopped it. This seems like expected behavior to me; at least, it is what I expected to see.
If I try to download part of a file (using, e.g.,
curl --range 10-10000000
) and then stop the download before it can finish, I don't see anything at all about it on the status page. If I let the request complete, I still don't see anything about it on the status page. Weird, arguably buggy behavior, but not what Zooko observed.Zooko: Can you reproduce these problems? If so, what am I doing wrong to not be able to reproduce them?
Brian changed some of the progress reporting of mutable files in changeset:9756146d61673552 but I suppose this can't have any effect on these immutables that I had trouble with. Anyway, leaving assigned to me to try to reproduce.
Zooko, did you fail to reproduce this, or did you not get chance to try to do so?
I haven't tried yet. Will try.