-
Notifications
You must be signed in to change notification settings - Fork 143
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
ARV glitches: "Failed to save edit: Edit conflict detected" #19
Comments
Can you see if the server actually in it's reply indicate that it's an alleged edit conflict? |
I only looked into it once and the issue disappeared before I could get anywhere, but at least the one time Walter Görlitz wrote that report the API must have actually reported an edit conflict: The section header he used, "Failed to save edit: Edit conflict detected", is assembled in morebits Since this problem is observable for minutes at a time, I'd suspect some cache or database lag issue here. |
There seems to be a bug in the server API related to editing specific page sections. If the calls to setPageSection are removed, this error should go away. |
synched, I'll tell folks to re-open if it still happens |
If it /is/ fixed we may want to report this to bugzilla.wikimedia.org. |
Disabled in c97229c due to bugs in the API returning edit conflicts; temporally, it seems related to #19, and I think 45ce088 may have been trying to fix the same thing. I'm not sure what the error was but that was nine years ago, and testing seems fine, so I'm hoping this is okay, sort of a test for the rest.
Disabled in c97229c due to bugs in the API returning edit conflicts; temporally, it seems related to wikimedia-gadgets#19, and I think 45ce088 may have been trying to fix the same thing. I'm not sure what the error was but that was nine years ago, and testing seems fine, so I'm hoping this is okay, sort of a test for the rest.
From
UAA & AIV reports sometimes can't be saved due to an alleged edit conflict. It tries to save two or three times, and then gives up.
I could reproduce it once, but the problem dissolved while I was trying to debug it. It re-manifests from time to time though.
The text was updated successfully, but these errors were encountered: