Last modified: 2014-04-07 09:58:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61917, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59917 - Chunked upload sometimes seems to not update status after assembly job
Chunked upload sometimes seems to not update status after assembly job
Status: NEW
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
1.23.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: chunked-upload
  Show dependency treegraph
 
Reported: 2014-01-10 18:53 UTC by Bawolff (Brian Wolff)
Modified: 2014-04-07 09:58 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bawolff (Brian Wolff) 2014-01-10 18:53:58 UTC
Splitting this from bug 36587 comment 64, bug 36587 comment 72

Steps to reproduce:
*Probably want to try this on test2.wikipedia.org. The upload pipeline on a local install (without swift, with different job queue set up) is rather different.
*Get a big file. Say about 400 MB. For example the latest version of [[commons:File:Konkani_Viswakosh_Vol2.pdf]].
*Upload it using chunked uploading. Using something like [[commons:User:Rillke/bigChunkedUpload.js]] can be more convenient than upload wizard.
*Upload using chunked api, making sure async option is specified
*Eventually progress will halt at the queuing stage
*File is listed at Special:UploadStash assembled, despite returning the wrong status to the upload script. You can use API to verify it is assembled properly by fetching either the file size, or the sha1 sum. I made a hacky script to do this - [[commons:User:Bawolff/stash.js]]
*Sending the publish api command works to publish file despite the API claiming not to be ready for that step.

I expect this has to do with storing info in _SESSION, and especially editing _SESSION from a cli script, is unreliable.
Comment 1 Tilman Bayer 2014-03-07 03:34:21 UTC
I think I may just have run into this bug (UploadWizard getting stuck at "Submitting details and publishing..." for much more than 1h). The file was visible in Special:UploadStash and I used the helpful tool described above (in Rillke's version [[commons:MediaWiki:EnhancedStash.js]], now linked as a button under Special:UploadStash. This uploaded the file successfully, but there was a subsequent issue with the creation of the file description page. see https://commons.wikimedia.org/wiki/File_talk:WMF_Monthly_Metrics_Meeting_March_6,_2014.ogv ).
Comment 2 Rainer Rillke @commons.wikimedia 2014-03-07 11:05:07 UTC
(In reply to Tilman Bayer from comment #1)
> subsequent issue with the creation of the file description page
Which is probably Bug 32551
Comment 3 Tilman Bayer 2014-04-07 09:58:10 UTC
FWIW, with this month's metrics video upload (https://commons.wikimedia.org/wiki/File:WMF_Monthly_Metrics_Meeting_April_3,_2014.ogv , 898MB) I encountered a similar issue again: UploadWizard got stuck at "Submitting details and publishing..." for more than 1h. Fortunately though, I noticed from my contributions list that the file was actually already published correctly right after the upload, including the file description page with the information that had been entered into UploadWizard. It's just that theh upload progress page at https://commons.wikimedia.org/wiki/Special:UploadWizard was not updated, and still shows the spinner and the "Submitting..." message right now.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links