Page MenuHomePhabricator

refreshGlobalimagelinks.php dies with "No transaction to commit"
Closed, DeclinedPublic

Description

Steps to reproduce:

  1. check out Extension:GlobalUsage
  2. add require call to LocalSettings.pgp
  3. run update.php
  4. run php extensions/GlobalUsage/refreshGlobalimagelinks.php

Querying links after (page_id, il_to) = (0, )
PHP Notice: DatabaseBase::commit: No transaction to commit, something got out of sync! [Called from DatabaseBase::commit in /vagrant/mediawiki/includes/db/Database.php at line 3464] in /vagrant/mediawiki/includes/debug/Debug.php on line 303
PHP Stack trace:
PHP 1. {main}() /vagrant/mediawiki/extensions/GlobalUsage/refreshGlobalimagelinks.php:0
PHP 2. require_once() /vagrant/mediawiki/extensions/GlobalUsage/refreshGlobalimagelinks.php:107
PHP 3. RefreshGlobalImageLinks->execute() /vagrant/mediawiki/maintenance/doMaintenance.php:109
PHP 4. DatabaseBase->commit() /vagrant/mediawiki/extensions/GlobalUsage/refreshGlobalimagelinks.php:99
PHP 5. wfWarn() /vagrant/mediawiki/includes/db/Database.php:3464
PHP 6. MWDebug::warning() /vagrant/mediawiki/includes/GlobalFunctions.php:1144
PHP 7. MWDebug::sendMessage() /vagrant/mediawiki/includes/debug/Debug.php:157
PHP 8. trigger_error() /vagrant/mediawiki/includes/debug/Debug.php:303

The link refresh is successful though, as far as I can tell.


Version: unspecified
Severity: normal

Details

Reference
bz64779

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:09 AM
bzimport added a project: GlobalUsage.
bzimport set Reference to bz64779.
bzimport added a subscriber: Unknown Object (MLST).

As long as this only happens in Vagrant and not a production environment (which is very different since the DB is accessed via a load balancer), I don't think this is a severe issue. The functionality of the extension does not seem to be impaired. Probably some transaction is committed twice, and the second is ineffective and raises this notice.

Krinkle changed the task status from Open to Stalled.Jul 29 2018, 1:11 AM
Krinkle subscribed.

@Tgr Can you check whether this still happens on current versions? Many issues of this type were fixed over the past two release cycles.

@Tgr Can you check whether this still happens on current versions? Many issues of this type were fixed over the past two release cycles.

Unfortunately closing this Phabricator task as no further information has been provided.

@Tgr: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action...Change Status dropdown. Thanks!