Last modified: 2014-04-04 16:15:03 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 T65498, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63498 - PHP Warning: Invalid argument supplied for foreach() in ApiQuerySiteinfo.php on line 351
PHP Warning: Invalid argument supplied for foreach() in ApiQuerySiteinfo.php...
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.23.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-03 19:21 UTC by Sam Reed (reedy)
Modified: 2014-04-04 16:15 UTC (History)
4 users (show)

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


Attachments

Description Sam Reed (reedy) 2014-04-03 19:21:57 UTC
PHP Warning:  Invalid argument supplied for foreach() in /usr/local/apache/common-local/php-1.23wmf19/includes/api/ApiQuerySiteinfo.php on line 351
Comment 1 Andre Klapper 2014-04-04 11:56:48 UTC
Reedy: How often does this happen (this question basically applies to every such bug report, hence adding such info in comment 0 would be very helpful).
Comment 2 Brad Jorsch 2014-04-04 16:15:03 UTC
I see exactly one occurrence of this warning message in the apache2.log files on fluorine since 2014-03-20, at 2014-04-03 19:02:40.

The line in question is getting the argument for foreach by calling $wgContLang->getMagicWords(). Presumably this is returning some non-array value (null or false, I'd guess) where it is documented to return only arrays.

I did try correlating API queries to meta=siteinfo&siprop=magicwords at around that time, but making the same queries to the same wikis did not result in the warning being logged again to apache2.log.

Given all that, I'd suspect some bit of weirdness with the l10n update and the moving of the last wikis from wmf19 to wmf20 that was happening around that time. I'm going to close this for now, please reopen if it shows up again and particularly if it's reproducible.

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


Navigation
Links