Feature #4051: [Workbench] Pipeline component display order should be controlled by sort_order attributes if present. - Arvados

Actions

Copy link

Feature #4051

closed

[Workbench] Pipeline component display order should be controlled by sort_order attributes if present.

Added by Peter Amstutz about 10 years ago. Updated about 10 years ago.

Status:

Rejected

Priority:

Normal

Assigned To:

Category:

Target version:

2014-10-29 sprint

Start date:

Due date:

% Done:

Estimated time:

Story points:

0.5

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 1 (0 open — 1 closed)

Actions

Copy link

Updated by Peter Amstutz about 10 years ago

Description updated (diff)

Actions

Copy link

Updated by Peter Amstutz about 10 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.

Actions

Copy link

Updated by Tom Clegg about 10 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.