Page MenuHomePhabricator

Flow getting "Failed contacting Parsoid" on Beta Cluster
Closed, ResolvedPublic


Sample error:

[f56d5af4] Exception Caught: Failed contacting Parsoid

Event Timeline

Looks to be some sort of problem either with the deployed code or the configuration of parsoid in beta labs:

ebernhardson@deployment-bastion:/data/project/logs$ curl
TypeError: Object function Date() { [native code] } has no method 'mow'
    at wt2html (/srv/deployment/parsoid/deploy/src/api/routes.js:362:41)
    at routes.get_article (/srv/deployment/parsoid/deploy/src/api/routes.js:752:2)
    at callbacks (/srv/deployment/parsoid/deploy/node_modules/express/lib/router/index.js:272:11)
    at /srv/deployment/parsoid/deploy/src/api/routes.js:569:3
    at /srv/deployment/parsoid/deploy/node_modules/es6-shim/es6-shim.js:1220:20
    at Object._onImmediate (/srv/deployment/parsoid/deploy/node_modules/es6-shim/es6-shim.js:1177:28)
    at processImmediate [as _immediateCallback] (timers.js:330:15)

Most likely they intend to call instead of Date.mow

greg renamed this task from Flow getting "Failed contacting Parsoid" on Beta Labs to Flow getting "Failed contacting Parsoid" on Beta Cluster.Mar 16 2015, 6:00 PM
greg set Security to None.

Change 197100 had a related patch set uploaded (by Arlolra):
T92859: s/mow/now/

Negative24 claimed this task.
Negative24 subscribed.

Merged change fixed the problem for Talk:Flow.