Feature #4051
closed
[Workbench] Pipeline component display order should be controlled by sort_order attributes if present.
Description
Pipeline components are stored in a hash. In Ruby, and in the YAML representation of components that is stored in the database, the ordering of hash keys is consistent. However, when the components are handled by other languages such as Python (for example, by arv-copy) the order of components is likely to get permuted because order is not guaranteed by json or for "dict" or "hash" types by the in most languages.
A fix to display the components with consistent ordering was implemented way back in March in ac2db7d4aa32a772d9f21db3f1a8a63b1ad0ca2f and reverted in April with 085e614c8e7d1a29e675cf839a1ce9d92ffc5d5c
Related issues
Updated by Peter Amstutz over 9 years ago
If it's really important that users be able to customize the sort order, we could add a sort-order field that takes precedence over a default sorting policy of topological+lexical sorting.
Updated by Tom Clegg over 9 years ago
- Tracker changed from Bug to Feature
- Subject changed from Order of pipeline components is not consistent to [Workbench] Pipeline component display order should be controlled by sort_order attributes if present.
Updated by Tom Clegg over 9 years ago
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Peter Amstutz over 9 years ago
- Status changed from New to Rejected
Duplicate. Moved over to #2992
Updated by Ward Vandewege over 9 years ago
- Target version changed from Arvados Future Sprints to 2014-10-29 sprint