Bug #4432
closed
[SDKs] When copying pipeline instances using arv-copy, the component jobs get re-arranged
Description
for example: qr1hi-d1hrv-k46opnhr3hovt7g, i expected BWA first and Haplotype caller last.
Related issues
Updated by Brett Smith over 9 years ago
- Subject changed from When copying pipeline instances using arv-copy, the jobs get re-arranged to [SDKs] When copying pipeline instances using arv-copy, the component jobs get re-arranged
- Category set to SDKs
- Target version set to Bug Triage
This happens because Ruby hashes retain the order of keys, but Python dictionaries do not. As long as the pipeline instance lives in the Ruby universe, the components stay in order. When Python reads it, it loses the ordering, and puts it back in the Ruby universe all jumbled.
Python has an OrderedDict in the collections module. One way to fix this problem might be to make sure apiclient uses that class when it converts API responses into objects.
Updated by Brett Smith over 9 years ago
- Status changed from New to Resolved
- Target version changed from Bug Triage to 2014-11-19 sprint
Bryan,
Turns out we already had an issue for this. Please watch #2992 if you're interested in following the development. I mentioned to Ward that we should prioritize the issue higher because it causes this surprising display behavior. Thanks.