Last modified: 2014-03-05 22:25:46 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 T64092, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62092 - Getting UsageException when viewing new wiki, caused by ApiRunJobs
Getting UsageException when viewing new wiki, caused by ApiRunJobs
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
JobQueue (Other open bugs)
1.23.0
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 62280 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-01 05:03 UTC by PiRSquared17
Modified: 2014-03-05 22:25 UTC (History)
5 users (show)

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


Attachments

Description PiRSquared17 2014-03-01 05:03:40 UTC
I was trying to create a new instance on wmflabs with MediaWiki, but when I tried to view it in a web browser I got the following error:

Full traceback. (http://tools.wmflabs.org/paste/view/8a73a0bb)
[2f66af1e] /w/index.php Exception from line 1366 of /srv/mediawiki/includes/api/ApiBase.php: Invalid or stale signature provided

Backtrace:

#0 /srv/mediawiki/includes/api/ApiRunJobs.php(54): ApiBase->dieUsage(string, string, integer)
#1 /srv/mediawiki/includes/api/ApiMain.php(862): ApiRunJobs->execute()
#2 /srv/mediawiki/includes/api/ApiMain.php(332): ApiMain->executeAction()
#3 /srv/mediawiki/includes/Wiki.php(649): ApiMain->execute()
#4 /srv/mediawiki/includes/Wiki.php(669): {closure}()
#5 /srv/mediawiki/includes/Wiki.php(451): MediaWiki->triggerJobs()
#6 /srv/mediawiki/index.php(49): MediaWiki->run()
#7 {main}

Bawolff narrowed down the problem to https://gerrit.wikimedia.org/r/#q,2ea4d7ae,n,z (indeed, git checkout 2ea4d7ae8c19f^ fixed the issue)
Comment 1 Bawolff (Brian Wolff) 2014-03-01 05:21:20 UTC
For me, the calling api internally code runs fine, however the header( "HTTP/1.0 204 No Content" ); part leaks to the main web request, making pages inaccesible.
Comment 2 Gerrit Notification Bot 2014-03-01 05:35:11 UTC
Change 116224 had a related patch set uploaded by Aaron Schulz:
Avoid API error/header leakage from jobs API

https://gerrit.wikimedia.org/r/116224
Comment 3 Gerrit Notification Bot 2014-03-01 05:49:25 UTC
Change 116224 merged by jenkins-bot:
Avoid API error/header leakage from jobs API

https://gerrit.wikimedia.org/r/116224
Comment 4 PiRSquared17 2014-03-01 14:01:24 UTC
Thanks!
Comment 5 Matthew Flaschen 2014-03-05 22:25:46 UTC
*** Bug 62280 has been marked as a duplicate of this bug. ***

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


Navigation
Links