-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve log and exception message #142
Comments
It will always be raised. Only the |
jugmac00
added a commit
that referenced
this issue
Apr 23, 2021
jugmac00
added a commit
that referenced
this issue
Apr 24, 2021
jugmac00
added a commit
that referenced
this issue
Apr 24, 2021
jugmac00
added a commit
that referenced
this issue
Apr 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When there is a newer transaction id on the client than on the server - for instance after a backup has been restored - following message gets logged:
"ClientStorageError: Client has seen newer transactions than server!"
The admin is left with this message and probably does not know how to recover a working state - as Zope is no longer usable.
What worked for me - and maybe is not always the best solution was to remove the zec file, cf
https://docs.plone.org/3/en/manage/troubleshooting/transactions.html#zeostorage-client-has-seen-newer-transactions-than-server
There may be other reasons for this error and maybe other recovery steps make more sense then.
From a quick glance tox is not setup to run coverage (see #123 ), and from looking at the code and the tests it seems the branch ("Cache newer than server") is untested.
Update
The branch gets covered by
ZEO/src/ZEO/asyncio/tests.py
Line 437 in a6c1ffc
Was hard to spot, as the test does neither check for the AssertionError nor for the log message.
ZEO/src/ZEO/asyncio/client.py
Lines 488 to 493 in bd7cd06
Also, the tests for ZEO seems to be quite flaky, cf #140
@jamadden made some good suggestions how to proceed:
#139 (comment)
[Removed wrong assumption about assert / AssertionError]
The text was updated successfully, but these errors were encountered: