api.serlo.org
api.serlo.org copied to clipboard
Revisions are mismatched after accepting them
What is wrong?
After accepting a new revision, the revision is not shown, but another one instead - sometimes even from another entity.
Steps to reproduce
It often happens together with e2e-test failures, but there is no recipe yet how to reproduce it.
How should it behave?
Accepting a revision should make this revision the current one, not a previous one.
Solution: Clear cache if entity after accepting a revision
It doesn't seem to occur a lot nowadays, does it? Closing the issue as stale. Please reopen if it happens again and we have a way of reproducing it.