id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,launchpad_bug 952,multiple simultaneous uploads of the same file,zooko,zooko,"As described in #950 (upload doesn't appear in the Recent Uploads Downloads page) and #951 (uploads aren't cancelled by closing the web page) I started an upload of a large (350 MB) file, then started a second upload of the same file. Later I discovered that both uploads were running: {{{ # 2010-02-14 18:38:58.761541Z [152794]: uploaded 266352528 / 353388984 bytes (75%) of your file. # 2010-02-14 18:39:06.215643Z [152863]: storage: allocate_buckets 5osshw7oonef6qlpvdvtmuskt4 # 2010-02-14 18:39:17.599753Z [152865]: uploaded 266483607 / 353388984 bytes (75%) of your file. # 2010-02-14 18:39:17.608450Z [152867]: peer selection successful for : placed all 26 shares, sent 23 queries to 13 peers, 20 queries placed some shares, 2 placed none, got 1 errors # 2010-02-14 18:39:17.610185Z [152868]: _send_shares, used_peers is set([, , , , , , , , , ]) # 2010-02-14 18:39:17.887869Z [152869]: starting # 2010-02-14 18:39:18.554996Z [152947]: uploaded 266614686 / 353388984 bytes (75%) of your file. # 2010-02-14 18:39:18.597406Z [153004]: uploaded 131079 / 353388984 bytes (0%) of your file. # 2010-02-14 18:39:21.569559Z [153081]: uploaded 266745765 / 353388984 bytes (75%) of your file. # 2010-02-14 18:39:21.610486Z [153138]: uploaded 262158 / 353388984 bytes (0%) of your file. }}} To close this ticket, make so a second upload of the same file (when using the same added convergence secret of course) just waits for the first upload instead of starting a second task (which will compete with the first one for resources).",defect,closed,major,eventually,code,1.6.0,duplicate,large upload usability performance,,