Last modified: 2014-06-23 16:07:11 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 T59922, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 57922 - updateSpecialPages.php - PHP Notice "No transaction to commit, something got out of sync!"
updateSpecialPages.php - PHP Notice "No transaction to commit, something got ...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Maintenance scripts (Other open bugs)
1.21.x
All All
: High normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 58095
Blocks:
  Show dependency tree / graph
 
Reported: 2013-12-03 13:13 UTC by [[kgh]]
Modified: 2014-06-23 16:07 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description [[kgh]] 2013-12-03 13:13:42 UTC 
After upgrading from MW 1.20.8 (PHP 5.3.3 and SQL 5.1.66) to 1.21.3 I get the following PHP notice for every special page to be updated:

PHP Notice:  UpdateSpecialPages::execute: No transaction to commit, something got out of sync! [Called from DatabaseBase::commit in /.../includes/db/Database.php at line 3068] in /.../includes/debug/Debug.php on line 283

$wgDevelopmentWarnings was set to true before and after the upgrade.

The special pages however are being updated.

I will also be nice to know how to get this in sync.
Comment 1 Marcin Cieślak 2013-12-06 14:31:49 UTC 
Can you try with $wgDevelopmentWarnings = false? The real error gets covered up because of bug 58095
Comment 2 [[kgh]] 2013-12-06 15:36:24 UTC 
This notice is only shown on shell or send by e-mail from cron when $wgDevelopmentWarnings is set to true. If set to false the expected behaviour is observed in the shell (log of special pages updated) and via cron no e-mail is sent.

Thank you for dealing with this.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links