Updating new-resolver-config branch - #1323
Conversation
Closes #978 Signed-off-by: Marcel Nadzam <mnadzam@redhat.com> Co-Authored-By: Cursor
When multiple_versions is enabled and some packages fail to bootstrap, write a partial-failures.json artifact to work-dir/ so downstream CI analysis tools can detect soft failures in jobs that exit successfully. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Ryan Petrello <rpetrell@redhat.com>
The .get() chain on resp.links returns str | None, which mismatched the str annotation on the pagination variable. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Ryan Petrello <rpetrell@redhat.com>
…res-report feat(bootstrapper): write partial-failures.json for multi-version mode
Document the new multi-version failure artifact, its schema, cleanup behavior, and interaction with test mode. Closes: #1320 Co-Authored-By: Codex <codex@openai.com> Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
…ures-docs docs: document partial-failures.json for multi-version bootstrap
test(metrics): add coverage for metrics timing decorator
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
rd4398
left a comment
rd4398
left a comment
There was a problem hiding this comment.
LGTM
I wonder we should auto-merge these updates in the future as the code is already merged on main branch
|
Tick the box to add this pull request to the merge queue (same as
|
4 participants
Pull Request Description
Why
We need to keep the new-resolver-config uptodate with main branch