Closed gwright99 closed 5 months ago
Also need to add that multiple filters can be concatenated and they work:
tw runs list \
--filter="after:2024-05-01T00:00:00.000Z before:2024-05-05T00:00:00.000Z" \
--workspace="seqeralabs/showcase"
Pipeline runs at [seqeralabs / showcase] workspace:
ID | Status | Project Name | Run Name | Username | Submit Date
----------------+-----------+----------------------+--------------------+------------+------------------------------
12qJlhI8eHTJ6M | SUCCEEDED | nf-core/rnaseq | boring_panini | esha-joshi | Fri, 3 May 2024 16:40:45 GMT
1IyAQIibMoLSE8 | SUCCEEDED | nf-core/rnaseq | angry_bernard | esha-joshi | Thu, 2 May 2024 19:43:40 GMT
3ytnGaw6UeSdp | SUCCEEDED | nf-core/rnaseq | sleepy_volta | esha-joshi | Thu, 2 May 2024 16:51:56 GMT
2MpiAQTGwMVU8R | SUCCEEDED | seqeralabs/nf-dragen | nostalgic_roentgen | esha-joshi | Wed, 1 May 2024 20:53:02 GMT
This issue has been linked to a Canny post: Allow the CLI command 'tw runs list' to filter by date :tada:
This filtering is done at server-side and it maps directly to the search capability described here: https://docs.seqera.io/platform/23.4.0/monitoring/overview#search
(when it was added to the CLI it was a simple "starts with", but now is much more powerful).
Agreed, but it doesn't match perfectly (for example, the before
and after
need to be fully qualified ISO 8601 datetimes and not just YYYY-MM-DD
). I've got a PR incoming.
The actual filtering occurring on payloads retrieved by the
tw cli
does not appear to be the same as how the help text describes the behaviour.How to reproduce
tw
version:0.9.1
Enterprise
Version 23.4.3_46971e7
Existing runs in workspace:
Displayed help text:
Expected outcome
A little unclear, actually.
The
--filter
text says "pipeline runs with names that start with", so I assume that'sRun Name
column? This is only partially true based on results, however.Actual outcome
Scenario 1: Successful filter based on
Run Name
:Scenario 2: Baseline scenario where nothing matches:
Scenario 3a: Search for key present in all lines (but not starting in all):
This works but doesn't seem to be matching on the start of the
Run Name
column.Scenario 3b: Search for key present in all lines (but not starting in all), with wildcard:
Scenario 4a: Search for full key exclusive in a column:
Scenario 4b: Search for full key with qualifier:
Scenario 4c: Search for partial key with qualifier:
Scenario 4d: Search for partial key with qualifier, with wildcard:
Conclusion
More filtering criteria must be getting applied behind the scenes. It would be good to be clear in the help text so folks don't need
trial-and-error
experimentation / reverse-engineer viatw -v ...
.