[QA] [Ops] Parsoid charset corruption post-mortem

Tue Nov 5 02:15:50 UTC 2013

(-cc wikitech-l, +cc QA)

On Mon, Nov 4, 2013 at 2:57 PM, Gabriel Wicke <gwicke at wikimedia.org> wrote:
> On 11/04/2013 12:58 PM, Erik Moeller wrote:
>> This was due to a broken deployment of Parsoid, the new MediaWiki
>> parser used by VisualEditor. A new library dependency defaulted to
>> iso8859-1 instead of utf-8, which caused character munging to occur.
>
> I have created a post-mortem at
> https://wikitech.wikimedia.org/wiki/Incident_documentation/20131104-Parsoid
>
> The most important recommendation is the creation of automated
> full-stack web API tests in addition to our existing parser test and
> round-trip test setups. This should catch library issues like this in
> the future before deployment.
>
> We also updated the Parsoid deploy guidelines to include manual edit
> checks on non-English wikis, which will help to catch any remaining
> production-specific deployment issues.

Hi Gabriel,

Can you explain how the release cycle works for Parsoid?  It would
seem implementing "Manually test VisualEditor on non-English wikis
before and after deployment" requires the team to have a better
understanding when that is.

Rob