Last modified: 2014-01-08 19:25:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61813, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59813 - Flow: Unable to make new posts
Flow: Unable to make new posts
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-08 02:09 UTC by Quiddity
Modified: 2014-01-08 19:25 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Quiddity 2014-01-08 02:09:32 UTC
Attempting to make a new post results in the error message:

"An error occurred.
The error message received was: An unexpected error occurred."

and logs of:
{"flow":{"reply":{"result":"error","errors":{"topic":{"readonly":{"message":"An unexpected error occurred.","extra":null}}}}}}

reproduced by huh, quiddity, and spage on Talk:Flow and Talk:Sandbox on mediawikiwiki
Comment 1 PiRSquared17 2014-01-08 02:10:24 UTC
For the record, huh is me.
Comment 2 Bingle 2014-01-08 02:27:29 UTC
The WMF core features team tracks this bug on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/flow/cards/702, but people from the community are welcome to contribute here and in Gerrit.
Comment 3 spage 2014-01-08 02:55:17 UTC
We blocked replies last night due to spam; we deployed latest Flow  with anti-spam code today, but it had an unrelated bug. In trying to revert that one bug we reverted back to last night.  Hence the errors you see on production wikis.
Comment 4 Maryana Pinchuk 2014-01-08 18:57:29 UTC
Quiddity, I sent an email about this last night :)

We tried to deploy AbuseFilter and spam blacklist patches yesterday during a lightning deploy window, but there was an unrelated issue that caused "lightning" to morph into "all-day cursing at the consoles." For the sake of Benny & Erik's sanity, I told them to just keep the two Flow pages frozen until the regularly-scheduled deployment train pushes out all the new changes (including the one to fix the new issue) on Thursday. Obviously, we wouldn't do this if there was a user base depending on Flow, but while it's still in a sandbox state and lots of people aren't giving feedback on it, this seems like the most sane solution.
Comment 5 Quiddity 2014-01-08 19:25:39 UTC
(In reply to comment #4)
> Quiddity, I sent an email about this last night :)
> 

...at 6:13PM - which was 4 minutes after I submitted this bug, and after we'd spent a while trying to diagnose the problem in IRC! :P

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links