pauses during streaming music at a party #193
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
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#193
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Sometimes tahoe pauses during streaming a succession of music files at a party. I think that the pauses always come right after someone has closed their laptop and started to leave the party.
The part about a download failing because one of its servers disappeared is a known issue.
But the part about pausing during a working download and then resuming about a minute later is strange. Also sometimes it pauses at the beginning of downloading a new file.
I think.
See also #253, #287, and #521.
The part of this that is understood enough to that we can make progress on it now lives in #287 (download: tolerate lost/missing peers). The part that isn't really #287 is that downloads would pause for about 60 seconds and then resume. I don't know how to explain that, but I haven't attempted to reproduce the problem in years and the code has changed a lot since then, so I'm going to presumptively close this ticket as 'wontfix'.
Brian intends to rewrite the downloader at some point to fix #287, optimize performance, etc. (I intend to do so as well, but I bet Brian gets around to following-through on his intention before I do...)