viewing web-status of unfinished immutable downloads causes exception #1160
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#1160
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?
The web-status view (visible at
<http://$GATEWAY/status>
) of immutable downloads shows "not impl yet" in the status column. If you click on that to get an exception which ends with:Attached is an incident report file from such an incident.
Attachment incident-2010-08-09-140456-fzgnluy.flog.bz2 (25484 bytes) added
Attachment patch-1-hush-logs.3.diff (909 bytes) added
don't log storage requests that arrive after the download is finished
Attachment patch-3-tolerate-unretired-DYHB.diff (3770 bytes) added
real fix for #1160: tolerate DYHB requests that haven't retired, plus tests
Accepting for review.
Attachment patch-2-fewer-downloadstatus.diff (6419 bytes) added
stop creating download-status objects for non-downloaded filenodes (v2)
Looks good, ok to apply with v2 of second patch.
In changeset:dc1afc81bbfe95de:
In [4693/ticket68-multi-introducer]: