Page MenuHomePhabricator

TypeError: parentDomElement is null / TypeError: data[i] is undefined at ve.dm.Converter.prototype.getDomSubtreeFromData
Closed, ResolvedPublic

Description

https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-2020.09.10/clienterror/?id=AXR28uxzMQ_08tQaM6VQ

logstash

at ve.dm.Converter.prototype.getDomSubtreeFromData <url>
at ve.dm.MWReferenceNode.static.toDomElements <url>
at ve.dm.CXReferenceNode.static.toDomElements <url>
at ve.dm.Converter.prototype.getDomElementsFromDataElement <url>
at ve.dm.Converter.prototype.getDomSubtreeFromData <url>
at ve.dm.Converter.prototype.getDomSubtreeFromModel <url>
at ve.dm.Converter.prototype.getDomFromModel <url>
at ve.dm.Surface.prototype.getDom <url>
at ve.ui.Surface.prototype.getDom <url>
at mw.cx.TargetArticle.prototype.getContent <url>
at mw.cx.TargetArticle.prototype.publish <url>
at mw.cx.TranslationController.prototype.publishArticle <url>
at mw.cx.TranslationController.prototype.publish <url>
at OO.EventEmitter.prototype.emit <url>
at ve.init.mw.CXTarget.prototype.onPublishButtonClick <url>
at ve.ui.CXPublishTool.prototype.onSelect <url>
at OO.ui.ToolGroup.prototype.onMouseKeyUp <url>
at OO.ui.ToolGroup.prototype.onDocumentMouseKeyUp <url>

Event Timeline

Jdlrobson renamed this task from TypeError: parentDomElement is null at ve.dm.Converter.prototype.getDomSubtreeFromData to TypeError: parentDomElement is null / TypeError: data[i] is undefined at ve.dm.Converter.prototype.getDomSubtreeFromData .Sep 15 2020, 7:58 PM
Nikerabbit added a subscriber: Nikerabbit.

This is potentially breaking publishing.

Pginer-WMF added a subscriber: santhosh.

This has been waiting for T244114: "Publish" button remains greyed out: "TypeError: this.translationView.categoryUI is null" to be verified, to see if its fix also fixed this.

Since there are not steps to reproduce here, we should check Logstash if this error goes down.

Note: it's not clear to me if this error can persist in saved drafts, if so, we would only see a gradual decline of these errors, not a sharp stop. That's important because we also need to consider if this the same issue or separate cause.

Jpita added a subscriber: Jpita.

Since there are not steps to reproduce here, we should check Logstash if this error goes down.

https://logstash.wikimedia.org/goto/245275b1b3e8993d5ad2eaae6da70e44
last error is from Feb 14.
is it safe to move this to done?

Pginer-WMF claimed this task.