Prevent String upload jobs from failing with "missing end-quote"
Bug #1674011 reported by
Julie Pichon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Expired
|
Undecided
|
Unassigned |
Bug Description
The CI post-merge job that pushes new strings over to Zanata has been failing for over a week with the following error:
2017-03-16 12:55:13.468428 | + zanata-cli -B -e push --copy-trans False
[...]
2017-03-16 12:55:15.391220 | [INFO] Found source documents:
2017-03-16 12:55:15.391405 | [INFO] i18n/messages
2017-03-16 12:55:15.531164 | [ERROR] Operation failed: missing end-quote
This means translators have not had the full set of strings to work from even for Ocata, and no new strings can be added to Zanata for either branch until this is fixed.
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
summary: |
- String upload job failing with "missing end-quote" + Prevent String upload jobs from failing with "missing end-quote" |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
To post a comment you must log in.
This seems to be due to a \n linebreak in one of the strings:
https:/ /github. com/openstack/ tripleo- ui/blob/ eb64c4/ src/js/ components/ deployment_ plan/Deployment Plan.js# L73
For now, to unblock the jobs I propose to simply remove it, since \n isn't recognised as a linebreak when the tooltip is displayed in the UI at the moment and simply adding <br/> has the tag itself appear in plain text.
The longer term solution would be to prevent such invalid strings from being created, either on our side or by fixing the json2pot tool upstream.