I got this error message when trying to reply to a post on https://ko.wikipedia.org/wiki/위키백과:사랑방_%28기술%29.
TypeError: Cannot read property 'linterrors' of undefined
I've seen it before in T259855#6369023.
Description
Description
I've seen it before in T259855#6369023.
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix error handling in controller#getPageData | mediawiki/extensions/DiscussionTools | master | +2 -0 |
Related Objects
Related Objects
- Mentioned In
- T259769: QA Reply Tool at "Phase 1" wikis
T259855: DiscussionTools touched unrelated parts of the page - Mentioned Here
- T261538: Revise HTTP 500 error message language
T236866: InvariantException: Invariant failed: Bad UTF-8 at start of string
T260180: RESTBase error 500 on a specific page on ko.wp: Wikimedia\Assert\InvariantException
T259855: DiscussionTools touched unrelated parts of the page
Event Timeline
Comment Actions
Change 619857 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
[mediawiki/extensions/DiscussionTools@master] Fix error handling in controller#getPageData
Comment Actions
Change 619857 merged by jenkins-bot:
[mediawiki/extensions/DiscussionTools@master] Fix error handling in controller#getPageData
Comment Actions
@matmarex: the "Error contacting the Parsoid/RESTBase server (HTTP 500)" language, which I understand this patch "re-instates"/ensures is properly displayed, how did that language come to be?
...I ask thinking any person encountering that error message is not likely to know what it means or what they can do to resolve it.
I appreciate any changes that result from the answer to the question above are likely out of scope for this task.
Comment Actions
The error message was added in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/544152, replacing a message that would just say "HTTP 500" with no context.
Generally, a person seeing this error can't do anything to resolve it. It's only caused by bugs in our code or our configuration.
The message exist only so that they have something concrete to refer to, e.g. when reporting the bug, and so that we can tell which error condition they ran into (that's why it's not something entirely vague like "Something went wrong").