You can clone with
HTTPS or Subversion.
Despite getting that error message (which I briefly see on everything I do with the develop script, but it usually gets overwritten before I can get a screenshot or good look at), the edit did save. The one above was using the "submit" button on a G13 eligible draft and selecting "original creator" (whom didn't get notified of the resubmission, but I'm not sure if that is suppose to happen but think it should), the one below was hitting "tag as G13".
I recognized the same, but I wasn't sure if that is again some major issue with the WMF servers...
I've been seeing it for a few days and I didn't see it when I was testing with the stable version yesterday to figure out why FFU wouldn't load at all. I'm on IRC.
Wonder if David's most recent report is associated with this bug.
I think mw.api() is being weird...
...once again, we need to look and see what specifically the error object contains
begone, erroneous editconflict messages; #194
Pretty sure above commit fixes this (at least it does for me). Please test with theobot mirror and mark as "fixed in develop."
@Technical-13 after clearing your cache i am 99% sure you won't see said edit conflict error. Please screengrab if it does occur; otherwise I am marking as fixed.
Has nothing to do with caching issues. I see it in Opera, Chrome, Firefox, and Firefox mobile on my Android.
Please give me a specific page and action to perform. The bug appeared because the script was making two POST requests instead of one; perhaps I neglected to fix that bug in a certain portion..?