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

Correctly sort ECRs when there are only two in the list #139

Merged
merged 1 commit into from
May 30, 2022

Conversation

ghost
Copy link

@ghost ghost commented Mar 3, 2022

SortByPublication had a bug where it was checking only one of the
candidates' versions but not the other. If there are only two
candidates to be sorted then one's version wasn't being examined so
the sort ended up being based on publish date only, ignoring the
version.

Now we check both candidates' versions so version is always the
primary sort key, even when there are only two candidates.

SortByPublication had a bug where it was checking only one of the
candidates' versions but not the other. If there are only two
candidates to be sorted then one's version wasn't being examined so
the sort ended up being based on publish date only, ignoring the
version.

Now we check both candidates' versions so version is always the
primary sort key, even when there are only two candidates.
@3scale-robot 3scale-robot added needs-kind Indicates a PR or issue lacks a `kind/foo` label and requires one. needs-priority Indicates a PR or issue lacks a `priority/foo` label and requires one. needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. size/S Requires less than a day to complete the PR or the issue. and removed needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. labels Mar 3, 2022
@ghost
Copy link
Author

ghost commented Mar 3, 2022

/kind bug

@3scale-robot 3scale-robot added kind/bug Categorizes issue or PR as related to a bug. and removed needs-kind Indicates a PR or issue lacks a `kind/foo` label and requires one. labels Mar 3, 2022
@raelga
Copy link
Contributor

raelga commented Mar 18, 2022

Thanks @acnodal-tc for the PR.

@roivaz
Copy link
Member

roivaz commented May 30, 2022

/assign

@roivaz
Copy link
Member

roivaz commented May 30, 2022

/ok-to-test

@3scale-robot 3scale-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 30, 2022
@roivaz
Copy link
Member

roivaz commented May 30, 2022

/lgtm
/approve

@3scale-robot 3scale-robot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2022
@3scale-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: fb739630a41f2f56c00423d5851610250d1f0149

@3scale-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: roivaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@3scale-robot 3scale-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 30, 2022
@3scale-robot 3scale-robot merged commit 6e97203 into 3scale-ops:main May 30, 2022
@ghost ghost deleted the sort-pairs branch June 10, 2022 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. needs-priority Indicates a PR or issue lacks a `priority/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Requires less than a day to complete the PR or the issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants