Closed splitbrain closed 7 years ago
Before this failure ckgedit had several successful language updates from the translation tool. I've tried to track down what might have changed between the successful ones and this failure but nothing stands out, and there's no problem cloning the plugin either from github or from repository to repository locally.
@turnermm, looking at your merged pull requests I got the impression that this issue is fixed?
@splitbrain or are there still points of attention left?
Yes, the issue was fixed. ckgedit has been receiving regular translation updates for at least (or about) one year. The latest was Japanese: https://github.com/turnermm/ckgedit/pull/104.
Errorcounter is only triggered for recognized errors:
/src/org/dokuwiki/translatorBundle/Services/Repository/RepositoryErrorReporter.php
:
if ($template !== '' && $repo->isFunctional()) {
$repo->getEntity()->setErrorCount($repo->getEntity()->getErrorCount() + 1);
$this->emailService->sendEmail(
$repo->getEntity()->getEmail(),
'Error during import of ' . $repo->getEntity()->getDisplayName(),
$template,
$this->data
);
return $this->emailService->getLastMessage();
} else {
return 'Unknown error:' .get_class($e);
}
RepositoryErrorReporter is used in update() and createAndSendPatch(), see https://github.com/dokufreaks/dokuwiki-translation/blob/master/src/org/dokuwiki/translatorBundle/Services/Repository/Repository.php#L103
Does this mean that ckgedit has crashed the translation tool? I had a Hungarian translation update as recently as May 15th. And no errors have been reported, to me, at least. I just tested and cloned a copy without any issues.
And I just further tested by syncing an old fork of ckgedit, that I keep on a test github account, with the current ckgedit repository. It merged without any issues.
With the information up to now and checking of some logs I don't recognize something that is (still) broken.
As described in https://forum.dokuwiki.org/thread/10897 (#53 somewhat related), the ckgedit plugin crashed the importer cronjob leaving a lockfile behind.
Neither setting the error count to 3 nor setting the state to inactive made the importer skip the defective plugin. This seems to be because the error was caused within a pending language update?
I have no idea what happened, but here is all the info I have.
The whole data of the plugin was copied to the
inspect
folder in the translation tool's home directory.This is what we got in the error log:
This is what the cronjob had as output (was sent via mail to me)
This was the entry for the pending update:
This was actual entry for the plugin: