Page MenuHomePhabricator
Create Task
Maniphest T60359

If token request fails hard (503) during save, user is stuck in limbo
Closed, ResolvedPublic
Actions

Description

Ran into this bug in Beta mode (on beta labs), but may also exist in stable.

I made an edit to an article, went to the preview screen, and then hit the button to save the edit. The GET request to the API to retrieve an edit token returned a 503 error (i.e. a Wikimedia error, not an API error). This left me in the "saving edit" state forever, with no way to escape other than hitting the back button and losing my edit.

Version: unspecified
Severity: major

Details

Reference
bz58359

Event Timeline

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:14 AM
• bzimport added a project: MobileFrontend-stable.
• bzimport set Reference to bz58359.
• bzimport added a subscriber: Unknown Object (MLST).
kaldari created this task.Dec 11 2013, 11:54 PM
• bzimport added a comment.Dec 12 2013, 12:05 AM

bingle-admin wrote:

Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1503

gerritbot added a comment.Dec 24 2013, 11:55 PM

Change 103615 had a related patch set uploaded by Kaldari:
Make sure we error out if token retrieval fails on save

https://gerrit.wikimedia.org/r/103615

gerritbot added a comment.Dec 25 2013, 12:12 AM

Change 103615 merged by jenkins-bot:
Make sure we error out if token retrieval fails on save

https://gerrit.wikimedia.org/r/103615

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits