-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort cylc show task proxies #6270
Sort cylc show task proxies #6270
Conversation
463f79b
to
ca9748a
Compare
It should have a test if we want to ensure that sorted output stays sorted in future. There's an integration test that tests |
Looks good though - thanks for the PR! |
I can have a look later. Timing matters as the results depend on graphql return order, so depending on what it is doing behind the scenes, they may come back "sorted" already. I can probably rig something up which always returns an unsorted order as I did for myself fairly easily manually. |
There are also some functional tests that literally run the script. |
(I just converted the PR to a Draft, since you literally had "DRAFT" in the title - makes it clearer when listening open PRs etc.) |
@ColemanTom If you would like this in the next 8.3 release, please rebase onto the |
Otherwise leave on the master branch and it will go into 8.4.0. Features normally go onto minor releases rather the bugfix releases, but this is so small we could go either way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I think this is ready to go (pending a milestone).
Tests wouldn't hurt, but sorting is non-functional so fair enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving the code change too. IMO it can go to 8.3.x (we can argue it was a bug that the output order is random).
8.3 vs 8.4 - I don't particularly care. Please advise which you want it to be in and I will do that. |
I assumed you'd prefer 8.3 so I was justifying that - because the next 8.3.x release will be soon, but 8.4.0 might be some time coming. Anyhow, might as well go for 8.3.x |
I've changed the milestone to 8.3.4. You just need to rebase your branch locally to 8.3.x, force-push it to GitHub, then change the PR base branch to 8.3.x via Edit (PR header) above. |
I'll try to do it tomorrow or otherwise early next week. The external platform I do development on has been down for maintenance all day. |
It was possible for taskProxies when doing 'cylc show' to be in an odd order: Task ID: 20240728T0000Z/b Task ID: 20240727T0000Z/b Task ID: 20240729T0000Z/b After this change, they are always sorted by the ID of the task: Task ID: 20240727T0000Z/b Task ID: 20240728T0000Z/b Task ID: 20240729T0000Z/b
ca9748a
to
fa526dd
Compare
Ok, pointing at 8.3.x now. I do want to add some tests, but I don't have the time right now but will have it in my backlog to look at when not trying to get some systems operational. |
I have some tests almost ready to go for this, so you're off the hook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Integration test added. Just need a final approval from you @oliver-sanders
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).?.?.x
branch.Closes #6266
Before
After
Still works for no matches
Notes
No tests added as I didn't think they were really needed.