ContentTranslation should not assume Parsoid is source of all VRS errors
Closed, ResolvedPublic
Actions

Description

Since CX uses VRS, the errors might be from either restbase or parsoid. See T112330.

		Status	Assigned	Task
		Resolved	• GWicke	T112330 In current VRS deployment scenarios, error logging should not assume Parsoid is the source of all errors.
		Resolved	santhosh	T112565 ContentTranslation should not assume Parsoid is source of all VRS errors

cscott raised the priority of this task from to Needs Triage.

cscott updated the task description. (Show Details)

cscott added a subscriber: cscott.

https://gerrit.wikimedia.org/r/237421 is a first step toward this, but there is still some work to do (see post-merge comments on that patch, for instance, and https://gerrit.wikimedia.org/r/238209).

Arrbee set Security to None.

What's the urgency of this?

Amire80 triaged this task as Normal priority.Sep 16 2015, 10:07 AM

Amire80 moved this task from Needs Triage to CX7 on the ContentTranslation board.

Change 242928 had a related patch set uploaded (by Cscott):
Clarify responsibility for Parsoid/RESTBase errors

Change 242928 merged by jenkins-bot:
Clarify responsibility for Parsoid/RESTBase errors

santhosh closed this task as Resolved.Oct 6 2015, 6:47 AM