cancelled downloads are marked incorrectly on the Recent Uploads/Downloads page #1173

Open
opened 2010-08-12 20:53:57 +00:00 by zooko · 10 comments

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.

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.
zooko added the
code-frontend-web
major
defect
1.8β
labels 2010-08-12 20:53:57 +00:00
zooko added this to the 1.8.0 milestone 2010-08-12 20:53:57 +00:00
Author

Attachment Tahoe-LAFS - Current Uploads_Downloads.html (2403 bytes) added

**Attachment** Tahoe-LAFS - Current Uploads_Downloads.html (2403 bytes) added
Author

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".

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".
Author

Attachment ended-idle-Tahoe-LAFS - Current Uploads_Downloads.html (1104 bytes) added

**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.

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.
Author

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.

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.
tahoe-lafs modified the milestone from 1.8.0 to 1.9.0 2010-09-04 13:13:38 +00:00
Author

Oh, if someone could do it real quick, we could fix this bug in v1.8.1. That would be nice!

Oh, if someone could do it real quick, we could fix this bug in v1.8.1. That would be nice!
zooko modified the milestone from 1.9.0 to 1.8.1 2010-10-22 13:40:23 +00:00
kevan commented 2010-10-24 19:09:45 +00:00
Owner

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?

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?
zooko self-assigned this 2010-10-24 20:54:44 +00:00
zooko modified the milestone from 1.8.1 to soon 2010-11-02 02:32:00 +00:00
Author

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.

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 removed their assignment 2012-02-02 22:12:27 +00:00
davidsarah commented 2012-04-01 23:17:45 +00:00
Owner

Zooko, did you fail to reproduce this, or did you not get chance to try to do so?

Zooko, did you fail to reproduce this, or did you not get chance to try to do so?
tahoe-lafs modified the milestone from soon to 1.11.0 2012-04-01 23:17:45 +00:00
zooko was assigned by tahoe-lafs 2012-04-01 23:17:45 +00:00
Author

I haven't tried yet. Will try.

I haven't tried yet. Will try.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1173
No description provided.