Skip to content
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

DM-42605: list chained collection children in search order #947

Merged
merged 1 commit into from Jan 24, 2024

Conversation

kfindeisen
Copy link
Member

@kfindeisen kfindeisen commented Jan 23, 2024

This PR fixes a bug where the TABLE mode of butler query-collections listed children in alphabetical order, obscuring the exact definition of a chained collection.

Checklist

  • ran Jenkins
  • added a release note for user-visible changes to doc/changes

Copy link

codecov bot commented Jan 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (92313a9) 88.39% compared to head (1007d69) 88.39%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #947   +/-   ##
=======================================
  Coverage   88.39%   88.39%           
=======================================
  Files         303      303           
  Lines       39082    39082           
  Branches     8237     8237           
=======================================
  Hits        34547    34547           
  Misses       3341     3341           
  Partials     1194     1194           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

("", "", "run1"),
("", "", "tag1"),
("", "", "chain2"),
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit odd that this test didn't catch the bug; how was the value of expected chosen?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume it's a classic case of:

  • Developer knows they're breaking the test for good reason.
  • Developer looks at the test output is after their change.
  • Developer thinks about whether that it reasonable and adopts it (but is subject to confirmation bias).

I suppose it's good that we were at least trying to test this before, even if we failed to do it correctly.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say this is a classic case of the problem definition being simple enough that you can work out the correct output in your head... 😬

("", "", "run1"),
("", "", "tag1"),
("", "", "chain2"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume it's a classic case of:

  • Developer knows they're breaking the test for good reason.
  • Developer looks at the test output is after their change.
  • Developer thinks about whether that it reasonable and adopts it (but is subject to confirmation bias).

I suppose it's good that we were at least trying to test this before, even if we failed to do it correctly.

The TABLE mode of butler query-collections, unlike the default TREE,
listed child collections in alphabetical order. This has now been
changed to match TREE's behavior. No changes were needed for FLATTEN,
which ignores chains anyway.
@kfindeisen kfindeisen merged commit 74df0db into main Jan 24, 2024
18 checks passed
@kfindeisen kfindeisen deleted the tickets/DM-42605 branch January 24, 2024 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants