-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Fix recommended release selection in an archived platform stream #46452
Fix recommended release selection in an archived platform stream #46452
Conversation
Maybe a stupid question but why are archived streams behaving differently? I mean why don't we keep the info around anyway? |
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.
Thanks @aloubyansky this is perfect!
$ qss update -S=3.17
[INFO] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[INFO]
[INFO] Suggested Quarkus platform BOM(s) update:
[INFO] + [io.quarkus.platform:quarkus-bom:pom:3.17.8] to add
[INFO] - [io.quarkus:quarkus-bom:pom:3.17.1] to remove
[INFO]
[INFO] Suggested extensions updates for 'io.quarkus.platform:quarkus-bom':
[INFO] ✔ io.quarkus:quarkus-arc (synced with BOM)
[INFO]
[INFO] Suggested extensions updates from other origins:
[INFO] ~ io.quarkiverse.roq:quarkus-roq-plugin-aliases:[1.3.0 -> 1.2.0]
[INFO] ~ io.quarkiverse.roq:quarkus-roq-plugin-series:[1.3.0 -> 1.2.0]
[INFO] ~ io.quarkiverse.roq:quarkus-roq:[1.3.0 -> 1.2.0]
[INFO] ~ io.quarkiverse.roq:quarkus-roq-plugin-tagging:[1.3.0 -> 1.2.0]
[INFO] ~ io.quarkiverse.roq:quarkus-roq-plugin-qrcode:[1.3.0 -> 1.2.0]
[INFO] ~ io.quarkiverse.roq:quarkus-roq-plugin-sitemap:[1.3.0 -> 1.2.0]
[INFO]
[INFO] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
First, not a stupid question. I am not sure what you mean by keeping the info around but there is indeed inconsistency that we could address. First, there is a split between recommended streams and the rest (what is referred to as "archived" in the test API). That's done to reduce the scope of metadata used when searching for releases that satisfy extension selection requirements. The difference is that when a user provides a stream option, we first check whether the stream is among the currently recommended streams (by calling https://registry.quarkus.io/q/swagger-ui/#/Client/get_client_platforms) or not, in which case we call https://registry.quarkus.io/q/swagger-ui/#/Client/get_client_platforms_all.
It can be solved in a few ways:
I think we'll end up implementing 3 at some point in the future. |
Note that for 2 and 3 with the option to limit to the recommended release, there may be an edge case that will break (I added a test for it in this PR with a comment). |
fyi @gastaldi |
Status for workflow
|
Fix #46436