Last modified: 2014-11-17 14:50:49 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 T74304, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72304 - Parsoid 0.1.15 generates 500 errors when editing pages
Parsoid 0.1.15 generates 500 errors when editing pages
Status: NEW
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All Linux
: Unprioritized major
: ---
Assigned To: Parsoid Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-21 12:44 UTC by Chris C
Modified: 2014-11-17 14:50 UTC (History)
9 users (show)

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


Attachments

Description Chris C 2014-10-21 12:44:36 UTC
This site, https://wiki.transitionnetwork.org/ is running on amd64 Debian Wheezy with Parsoid installed using apt as per the instructions at https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64

Today the new GPG siging key was installed and Parsoid updated (see https://trac.transitionnetwork.org/trac/ticket/692#comment:103 ) to version 0.1.15 and this has caused all edits using the VisualEditor to generate 500 errors, this is what is logged when you try to save a page:

[info][localhost/Sandbox2?oldid=946] started parsing
[fatal/request][localhost/Sandbox2?oldid=946] undefined is not a function
TypeError: undefined is not a function
    at TreeBuilder.resetState (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:61:17)
    at new TreeBuilder (/usr/lib/parsoid/src/lib/mediawiki.HTML5TreeBuilder.node.js:28:7)
    at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:231:17)
    at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:227:17)
    at ParserPipelineFactory.getPipeline (/usr/lib/parsoid/src/lib/mediawiki.parser.js:363:15)
    at ParserPipelineFactory.parse (/usr/lib/parsoid/src/lib/mediawiki.parser.js:311:20)
    at /usr/lib/parsoid/node_modules/prfun/lib/index.js:436:24
    at new Promise (/usr/lib/parsoid/src/node_modules/es6-shim/es6-shim.js:1228:11)
    at /usr/lib/parsoid/node_modules/prfun/lib/index.js:419:14
    at /usr/lib/parsoid/src/api/routes.js:152:62

The error presented to editors is:

Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?

I have reverted to the old version of parsoid to get around this issue:

apt-get install parsoid=0.1.12

There are some more details on this ticket https://trac.transitionnetwork.org/trac/ticket/799
Comment 1 James Forrester 2014-10-21 18:04:47 UTC
This sounds like it's caused by the silently-breaking-change made by one of the upstream npm modules – Parsoid team, could you advise?
Comment 2 C. Scott Ananian 2014-10-22 02:53:39 UTC
Yes, looks to me like a conflict with the html5 library. I don't know much about our Debian packaging though.
Comment 3 ssastry 2014-11-17 14:50:49 UTC
gwicke: Any clue about the published debian package? Is this just a matter of updating the debian package?

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


Navigation
Links