Last modified: 2013-11-06 13:05:29 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 T58606, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56606 - Autoloader wrongly spams wfDebug
Autoloader wrongly spams wfDebug
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (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: 2013-11-05 07:35 UTC by Jeroen De Dauw
Modified: 2013-11-06 13:05 UTC (History)
4 users (show)

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


Attachments

Description Jeroen De Dauw 2013-11-05 07:35:12 UTC
When the MW autoloader comes across a class it does not know, it calls wfDebug. This means that when using a PHP library that has its own autoloader, the log gets dumped full of useless warnings. Seen this on Jenkins quite a few times for a lot of the code used by the Wikidata related components. 

I just noticed a hack in the SMW autoloader to work around this deficiency: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/SemanticMediaWiki.php#L77

It is quite ridiculous this is needed however, and it is not a viable solution for libraries that are independent from MediaWiki.

This is under API because a component needs to be selected while none are appropriate. Another bug I guess.
Comment 1 Brad Jorsch 2013-11-05 14:59:26 UTC
(In reply to comment #0)
> This is under API because a component needs to be selected while none are
> appropriate. Another bug I guess.

So you picked a random entirely-unrelated component, instead of using "General/Unknown" which is specifically intended for this situation?

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


Navigation
Links