Last modified: 2013-07-31 01:45:55 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 T54293, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52293 - SMW master giving error in runJobs.php
SMW master giving error in runJobs.php
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-30 20:05 UTC by Jamie Thingelstad
Modified: 2013-07-31 01:45 UTC (History)
4 users (show)

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


Attachments

Description Jamie Thingelstad 2013-07-30 20:05:09 UTC
I just updated master branch of SMW this morning and I've now seen a few of these errors coming from my runJobs cron job:

PHP Fatal error:  Call to a member function getTimestamp() on a non-object in /srv/www/mediawiki/public_html/w/extensions/SemanticMediaWiki/includes/BasePropertyAnnotator.php on line 172

Have not investigated further yet, but wanted to get this out there quickly.
Comment 1 Gerrit Notification Bot 2013-07-30 23:16:00 UTC
Change 76853 had a related patch set uploaded by Mwjames:
(Bug 52293) use wikiPage instead if subject object

https://gerrit.wikimedia.org/r/76853
Comment 2 Gerrit Notification Bot 2013-07-30 23:21:15 UTC
Change 76853 merged by jenkins-bot:
(Bug 52293) use wikiPage instead if subject object

https://gerrit.wikimedia.org/r/76853
Comment 3 MWJames 2013-07-30 23:23:12 UTC
Thanks for testing.

PS: This sort of thing will also happen if you test the wrong object (as in the case above).
Comment 4 Jamie Thingelstad 2013-07-31 01:45:55 UTC
Thanks. I only saw this error thrown 3 times, and I'm not sure how to trigger it so sadly I cannot easily confirm resolution.

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


Navigation
Links