Display active HTTP upload operations on the status page #1032
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1032
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?
When a tahoe client uploads a file to a tahoe gateway via the WAPI, the status page on the gateway doesn't show it as an active operation until the file was entirely received.
It would be useful to see which active uploads are taking place and the amount of data that was already received by the gateway.
Good idea.
#950 (upload doesn't appear in the Recent Uploads Downloads page) was a less well-explained duplicate of this. This is closely related to #320 (add streaming (on-line) upload to HTTP interface). I suspect that we won't be able to implement this ticket very well without solving the issue that #320 is blocked on of getting access to the partially-uploaded data in twisted.web. See also #951 (uploads aren't cancelled by closing the web page) and #952 (multiple simultaneous uploads of the same file).
I disagree that we should consider this to be blocked on #320 (or #1288 which #320 is itself blocked on). It should be possible to give some indicator of progress, even without implementing streaming upload.