Bug 712281 - REST interface should accept TextFlowTargets in any order
Summary: REST interface should accept TextFlowTargets in any order
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: zanata-dev-internal
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-10 06:05 UTC by Sean Flanigan
Modified: 2012-01-27 01:44 UTC (History)
1 user (show)

Fixed In Version: 1.4
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-01-27 01:44:14 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 711249 0 unspecified CLOSED Import should skip over obsolete translations 2021-02-22 00:41:40 UTC

Internal Links: 711249

Description Sean Flanigan 2011-06-10 06:05:22 UTC 
TranslationResourcesService currently responds with "400 (Bad Request): Unexpected target: {resId}" when a TextFlowTarget is received after all TextFlows have been visited in order.  It requires all TFTs to be listed in the same order as their TFs, with no extras.  We should remove this undocumented requirement/assumption, and allow REST clients to provide TFTs in any order.
Comment 1 Ding-Yi Chen 2011-07-28 01:29:13 UTC 
Can you shed any light on how to reproduce it and verify it?
Comment 2 Sean Flanigan 2011-07-28 04:10:32 UTC 
It's an API change, so coding against the API is the only way to test it directly.  But I think the problem could probably be reproduced by running the python client to push PO files to an old version of Zanata server, if you hand-edit the PO files so that the messages are out of order compared to the POT.  We normally avoid this by running msgmerge, which puts the PO messages into the POT order.
Comment 3 Sean Flanigan 2012-01-27 01:44:14 UTC 
Fixed in 1.4
Note You need to log in before you can comment on or make changes to this bug.