Looks like both the fa_storage_key and fa_sha1 are blank, so no luck :(

@WMDE-leszek - Don't forget to add yourself as the Session Leader above (or ping anyone you think might want to lead this).

@Jrbranaa - Great! Please add yourself as the session leader above and flesh out the description as needed.

@Etonkovidova - That sounds great. I'll change the title and description to focus on the QA aspect. Please add yourself as the session leader above and feel free to add more details to the description (or change it completely).

@Mooeypoo, @Krinkle - We need someone to own this by Friday or it probably won't get approved as an official session.

@WMDE-leszek or @Bmueller - Haven't heard from @RazShuty. Do you know if anyone else at WMDE might be interested in presenting on this topic?

@brion - Any ideas on this or who would be good to ask?

@WMDE-leszek - This seems like a good session idea. Can you format it to match the other session proposals and put yourself as the session leader if you're interested in leading it?

@Jrbranaa @D3r1ck01 - Would either or both of you be interested in leading this session?

@Mooeypoo @WMDE-leszek - Would either or both of you be interested in leading this session?

@Volans, @Etonkovidova - Would either (or both) of you be interested in leading this session?

@RazShuty - Would you be interested in leading this session?

@WMDE-leszek - Thanks for the feedback. I've updated the session description accordingly.

@Nikerabbit @Darenwelsh - You both mentioned 3rd party development and support in your survey responses. Would either (or both) of you be interested in leading this session?

@Mooeypoo @daniel @Krinkle - Any of y'all want to be session leaders or facilitators for this? Feel free to ping other folks as well.

I'm running Chrome with AdBlock and PrivacyBadger.

@Tchanders - The reason provided for the global block was "Cross-wiki vandalism: If you cannot edit, please contact Stewards", although I'm not sure if that is stored in the same way that local block reasons are.

I was probably using VE, since I usually use VE on mobile unless it's something that specifically requires Wikitext editing.

This bug never should have been merged with T8271, as what it is asking for is fundamentally different. The most fundamental difference is that footnotes normally require references within them, and since it isn't possible to include references within references, the most common use case doesn't work with reference groups. This is why you will almost never see the <ref group...> syntax on Wikipedia. Instead they resort to complicated templates like {{efn}}, {{notelist}, {{NoteTag}}, {{NoteFoot}} etc. that use the obscure {{#tag:ref}} trick behind the scenes. Many Wikipedias don't have these templates, so there is no obvious way to create separate footnotes and references.

@mobrovac - Can you see how many folks are currently getting this error (per day), now that we have some work-arounds in place. Just wondering how severe the problem is at this point.

@Ryasmeen - Can you reproduce this bug? (Note that it's specifically happening when there is an edit conflict and the two-column edit conflict beta feature is active.)

@Waddie96 - I've reopened your original bug report and made the title more specific.

Reopening since T230272 has been resolved, but this error is still occurring according to reports. This may be a different underlying issue.

@Whatamidoing-WMF - Can you communicate to the communities that were discussing this bug (at least Italian and English Wikipedia) that it has been fixed (more or less)? Thanks!

We should probably split off a specific ticket for "Mechanism to remove geo data from EXIF of pre-existing images" as that workflow will be slightly different than removing it during upload (and possibly contentious).

The html parameter that was sent to the API for my edit request began with rawdeflate, in case that's a clue. Not sure if that's always the case or was an anomaly.

Thanks for digging into this @mobrovac. Marking Unbreak Now, since this is potentially losing ~2,000 edits per day. (Once you hit this error, there is no way to save your edit without copying it into a new window.)

@matmarex - That could be the case. The article I edited had been edited 5 hours previously (just to set a baseline).

I'm also pretty confident that the edit I ran into this bug with didn't involve an edit conflict or page move. Nor do I have the Two column edit conflict beta feature enabled.

Boldly marking this High priority since folks are losing edits, and, according to IndyJr, the bug happens "very frequently".

This task may make more sense once we migrate to psuedo-users.

@Theklan - I forgot to mention an important detail. In order to use the script, your account has to have the upload_by_url right, which is grants to the following user groups: autopatrollers, image reviewers, patrollers, and administrators. Sorry I forgot about that.

@Theklan - Clear your cache and try it again now. Which page are you trying on?