Run Copr builds directly and use LLMs only for diagnosis by opohorel · Pull Request #808 · packit/ai-workflows

opohorel · 2026-09-08T12:35:08Z

Call the existing build tool deterministically so successful builds no longer require model orchestration. Share the structured Copr result schema and invoke a diagnosis-only agent for failed builds with logs.

Migrate backport, inheritance, rebase, MR updates, and consolidation while preserving their timeout and retry policies. Keep rebuild and the incremental backport repair loop unchanged.

Add regression tests for gateway decoding, zero-LLM success handling, error classification, cancellation, and diagnosis without resubmission. Document the shared build flow and its dry-run behavior.

Validation: 64 focused container tests passed; Ruff lint and format checks passed. Broader container testing found two gateway startup test failures and the same missing-MCP-settings error in the install smoke test. The gateway test failures also reproduce on unchanged commit 00d2ba6. Other component suites passed.

Assisted-by: Codex

I've ran e2e test for build succeeding on first try and build failing on the first time with the need to fix it. No regressions were found. GPT-6 Astra estimates around 8% of token cost savings per backport task.

qodo-for-packit · 2026-09-08T12:36:16Z

PR Summary by Qodo

Run Copr builds deterministically with diagnosis-only LLMs

✨ Enhancement 🧪 Tests 📝 Documentation 🕐 40+ Minutes

AI Description

• Executes Copr validation deterministically, eliminating LLM calls for successful builds.
• Restricts LLM usage to diagnosing failed builds while preserving workflow policies.
• Shares build schemas and adds regression coverage plus operational documentation.

Diagram

sequenceDiagram
    participant W as Workflow agents
    participant H as Shared run_build
    participant G as MCP gateway
    participant C as Copr tool
    participant A as Failure analyst
    W->>H: Validate SRPM
    H->>G: Call build_package
    G->>C: Submit and poll
    C-->>G: Build result
    G-->>H: Structured BuildResult
    alt Build succeeds
        H-->>W: Success without LLM
    else Failure has logs
        H->>A: Diagnose existing failure
        A-->>H: Error explanation
        H-->>W: Failed build outcome
    else Timeout, tool error, or no logs
        H-->>W: Classified failure
    end

High-Level Assessment

The centralized deterministic helper is the strongest approach because build submission and status classification are deterministic operations, while LLM reasoning remains limited to log interpretation. Retaining full model orchestration would preserve unnecessary cost and nondeterminism, while moving diagnosis into the Copr tool would couple infrastructure execution to optional model availability.

Files changed (12) +521 / -137

Enhancement (1) +100 / -25

build_agent.pySeparate deterministic builds from LLM failure diagnosis +100/-25

Separate deterministic builds from LLM failure diagnosis

• Adds run_build to invoke build_package once, validate structured results, and classify successes, timeouts, infrastructure errors, and failures without logs. Restricts the renamed BuildFailureAnalyst to log retrieval and diagnosis, retaining original errors when analysis fails and allowing cancellation to propagate.

ymir/agents/build_agent.py

Refactor (6) +66 / -86

backport_agent.pyRoute backport and inheritance builds through run_build +15/-27

Route backport and inheritance builds through run_build

• Replaces model-orchestrated build agents with the shared deterministic helper for ordinary backports and Y-stream inheritance. Existing success, timeout, and incremental repair routing remains intact.

ymir/agents/backport_agent.py

merge_request_agent.pyUse deterministic validation for MR updates +8/-15

Use deterministic validation for MR updates
• Migrates merge-request update validation from a build agent invocation to the shared run_build helper while preserving existing workflow routing.
ymir/agents/merge_request_agent.py

mr_consolidation_agent.pyUse deterministic validation for MR consolidation +9/-18

Use deterministic validation for MR consolidation
• Replaces consolidation's prompted build agent with run_build. Existing retry selection, attempt accounting, and success requirements remain owned by the consolidation workflow.
ymir/agents/mr_consolidation_agent.py

rebase_agent.pyRoute rebase builds through run_build +8/-15

Route rebase builds through run_build
• Migrates rebase validation to deterministic build execution while retaining existing success and timeout transitions.
ymir/agents/rebase_agent.py

models.pyShare structured build and diagnosis schemas +25/-2

Share structured build and diagnosis schemas

• Moves the Copr BuildResult contract into common models and introduces dedicated failure-analysis input and output schemas. Clarifies that BuildOutputSchema carries workflow routing status with optional diagnosis.

ymir/common/models.py

copr.pyReuse the shared Copr result model +1/-9

Reuse the shared Copr result model
• Removes the tool-local BuildResult definition and imports the shared schema used by both the Copr tool and workflow callers.
ymir/tools/privileged/copr.py

Tests (2) +316 / -11

test_build_agent.pyCover deterministic execution and diagnosis boundaries +287/-0

Cover deterministic execution and diagnosis boundaries

• Adds regression tests for dictionary and JSON gateway responses, zero-LLM success handling, timeout and infrastructure classification, malformed payloads, cancellation, and diagnosis fallback. Also verifies that the analyst cannot submit builds or edit package content.

ymir/agents/tests/unit/test_build_agent.py

test_jinja2_templates.pyUpdate tests for diagnosis-only build templates +29/-11

Update tests for diagnosis-only build templates
• Updates template fixtures and assertions to use failed-build analysis inputs. Verifies that rendered prompts include structured failure details, artifact URLs, serialized paths, and no-resubmission instructions.
ymir/agents/tests/unit/test_jinja2_templates.py

Documentation (1) +20 / -0

README-agents.mdDocument deterministic Copr validation behavior +20/-0

Document deterministic Copr validation behavior

• Documents the shared build flow, diagnosis-only agent, workflow-specific timeout policies, and unchanged rebuild paths. Clarifies that dry-run mode still performs real build validation.

README-agents.md

Other (2) +19 / -15

instructions.j2Constrain the agent to failed-build diagnosis +14/-14

Constrain the agent to failed-build diagnosis

• Reframes instructions around analyzing an already-failed build and explicitly prohibits resubmission, source changes, or status decisions. Retains gateway extractor and legacy URL-based log inspection guidance.

ymir/agents/prompts/build/instructions.j2

prompt.j2Supply existing build results to the analyst +5/-1

Supply existing build results to the analyst
• Changes the prompt from requesting a build to requesting diagnosis of an existing failure. Includes the structured build result and artifact URLs for analysis.
ymir/agents/prompts/build/prompt.j2

qodo-for-packit · 2026-09-08T12:39:17Z

Code Review by Qodo

🐞 Bugs (3) 📘 Rule violations (1) 📜 Skill insights (0)

1. Consolidated builds never reach Copr 🐞 Bug ≡ Correctness

Description

run_build_agent passes state.jira_issue directly into BuildInputSchema, even though
consolidation sets that value to None when the selected branches contain no Jira footers. The
deterministic call forwards the null value to build_package, whose input schema requires a string
Jira issue, so those consolidations exhaust build retries without submitting a Copr build.

Code

ymir/agents/mr_consolidation_agent.py[R782-787]

+                build_output = await run_build(
+                    build_input=BuildInputSchema(
+                        srpm_path=state.consolidation_result.srpm_path,
+                        dist_git_branch=dist_git_branch,
+                        jira_issue=state.jira_issue,
+                    ),

Relevance

●●● Strong
Null propagation into a required downstream build field is a concrete workflow failure; recent
history accepts defensive validation.
PR-#726
PR-#611

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The new call forwards state.jira_issue; consolidation explicitly assigns it to None if footer
collection yields no Jira keys, while the build tool declares jira_issue as a required str and
uses it as projectname for the Copr project.
ymir/agents/mr_consolidation_agent.py[690-707]
ymir/tools/privileged/copr.py[85-88]
ymir/tools/privileged/copr.py[142-148]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The deterministic consolidation build invocation can pass `None` as `jira_issue`, but the `build_package` tool requires a string and uses it as its Copr project name. This makes valid consolidations whose commits have no Jira footer fail before a build is submitted.

## Issue Context
`fork_and_prepare_dist_git` intentionally derives `state.jira_issue` from collected commit footers and leaves it unset when none exist. Preserve existing behavior for consolidations that do not have a Jira issue by deriving a valid stable build/project identifier or otherwise handling that case before calling the build tool.

## Fix Focus Areas
- ymir/agents/mr_consolidation_agent.py[782-789]
- ymir/tools/privileged/copr.py[85-88]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Copr schema moves without a unit test 📘 Rule violation ▣ Testability ⭐ New

Description

copr.py now imports the shared BuildResult, but no new or updated privileged-tool unit test
asserts that BuildPackageTool uses that schema. The new gateway tests construct serialized results
independently of the Copr tool, so reverting the tool to its private result model would leave them
passing.

Code

ymir/tools/privileged/copr.py[26]
+from ymir.common.models import BuildResult

Relevance

●●● Strong
Privileged-tool changes commonly receive added unit coverage; this schema migration lacks direct
Copr integration testing.
PR-#670
PR-#655

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
Compliance rule 1589 requires new or updated unit coverage whenever a privileged tool changes. The
privileged Copr module now imports the shared result schema, while the existing Copr test imports
only the tool classes and the newly added agent tests validate separately constructed gateway
payloads rather than this privileged-tool integration.
Rule 1589: Require unit tests for changes to privileged tools (ymir/tools/privileged/, esp. distgit.py)
ymir/tools/privileged/copr.py[26-26]
ymir/tools/privileged/tests/unit/test_copr.py[13-22]
ymir/agents/tests/unit/test_build_agent.py[18-20]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Copr privileged tool now uses the shared `BuildResult`, but its unit tests do not verify that schema integration.

## Issue Context
Add a focused assertion that exercises `BuildPackageTool` and confirms its output uses or validates against the shared model, so restoring the former private schema would fail the test.

## Fix Focus Areas
- ymir/tools/privileged/tests/unit/test_copr.py[13-22]
- ymir/tools/privileged/copr.py[26-26]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. Failed builds lose log diagnosis 🐞 Bug ☼ Reliability

Description

create_build_failure_agent disables every local fallback whenever extract_log_snippets exists,
even when the required download_artifacts tool is absent. With that partial gateway tool set,
extraction is constrained to follow an unavailable download operation, so diagnosis cannot inspect
the Copr logs and retains only the generic build error.

Code

ymir/agents/build_agent.py[R176-179]

+    local_tools = (
+        []
+        if has_extract_log_snippets
+        else [

Relevance

●●● Strong
Partial gateway tool availability can strand diagnosis; accepted precedents favor defensive fallback
handling for missing optional data.
PR-#726
PR-#571

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The agent derives has_extract_log_snippets from the extractor alone, constrains that extractor to
run only after download_artifacts, and removes local tools whenever the extractor is present. The
prompt confirms that gateway-downloaded logs are accessible only through extraction, while gateway
registration shows the extractor is optional and separately sourced from the standard downloader.

ymir/agents/build_agent.py[155-185]
ymir/agents/prompts/build/instructions.j2[7-20]
ymir/tools/gateway_utils.py[73-86]
ymir/tools/privileged/gateway.py[104-117]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Failed-build diagnosis selects the gateway-only log path based solely on `extract_log_snippets`, although that tool cannot inspect Copr logs until `download_artifacts` has downloaded them. If only the extractor is advertised, the agent receives neither a usable gateway path nor the local URL-based fallback tools.

## Issue Context
Treat the gateway extraction path as available only when both `download_artifacts` and `extract_log_snippets` are present. Otherwise retain the local tools and render the fallback instructions; add coverage for the extractor-without-downloader combination.

## Fix Focus Areas
- ymir/agents/build_agent.py[155-185]
- ymir/agents/tests/unit/test_build_agent.py[401-421]
- ymir/agents/prompts/build/instructions.j2[7-20]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

4. A missing build tool aborts every job 🐞 Bug ☼ Reliability

Description

run_build delegates name resolution to run_tool but catches only ToolError, while run_tool
uses next(...) and raises when build_package is absent. If the gateway advertises an incomplete
tool set during a partial deployment or version mismatch, backport, rebase, inheritance,
merge-request update, and consolidation workflows receive an exception instead of the intended
infrastructure-failure result.

Code

ymir/agents/build_agent.py[R56-58]

+    except ToolError as e:
+        logger.warning("Copr build tool failed for %s: %s", build_input.jira_issue, e)
+        return BuildOutputSchema(success=False, error=str(e), is_infra_error=True)

Relevance

●●● Strong
Recent accepted findings prioritize preventing workflow aborts and handling downstream failures
explicitly.
PR-#726
PR-#611

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The changed helper catches only ToolError, but the shared lookup resolves string tool names with
an unguarded next, so an absent build_package never reaches that handler. Gateway tools are
dynamically obtained and passed directly into the new helper, making the changed path dependent on
that lookup behavior.
ymir/agents/build_agent.py[50-58]
ymir/common/utils.py[85-104]
ymir/agents/backport_agent.py[577-585]
ymir/agents/backport_agent.py[1125-1133]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`run_build` catches `ToolError`, but `run_tool` raises from `next(...)` when the requested gateway tool is absent. Convert missing-tool lookup failures into a structured infrastructure failure without swallowing malformed build-result validation errors or cancellation.

## Issue Context
The deterministic build path now directly resolves `build_package` from the gateway's advertised tool list. An incomplete gateway tool set must follow existing workflow infrastructure-error routing rather than aborting the graph.

## Fix Focus Areas
- ymir/agents/build_agent.py[50-58]
- ymir/common/utils.py[85-104]
- ymir/agents/tests/unit/test_build_agent.py[97-109]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Context sources

✅ Compliance rules (platform): 8 rules

Review mode: 🧠 Deep: This push introduces a substantial shared build workflow with schema decoding, async cancellation, diagnosis routing, and multiple independent caller integrations, creating several easy-to-miss behavioral risks.

Tip of the day

💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab)

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Previous reviews

Review updated until commit 7d732f1 🧠 Deep

Results up to commit e911d1c 🧠 Deep

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. A missing build tool aborts every job 🐞 Bug ☼ Reliability

Description

run_build delegates name resolution to run_tool but catches only ToolError, while run_tool
uses next(...) and raises when build_package is absent. If the gateway advertises an incomplete
tool set during a partial deployment or version mismatch, backport, rebase, inheritance,
merge-request update, and consolidation workflows receive an exception instead of the intended
infrastructure-failure result.

Code

ymir/agents/build_agent.py[R56-58]

+    except ToolError as e:
+        logger.warning("Copr build tool failed for %s: %s", build_input.jira_issue, e)
+        return BuildOutputSchema(success=False, error=str(e), is_infra_error=True)

Relevance

●●● Strong
Recent accepted findings prioritize preventing workflow aborts and handling downstream failures
explicitly.
PR-#726
PR-#611

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The changed helper catches only ToolError, but the shared lookup resolves string tool names with
an unguarded next, so an absent build_package never reaches that handler. Gateway tools are
dynamically obtained and passed directly into the new helper, making the changed path dependent on
that lookup behavior.
ymir/agents/build_agent.py[50-58]
ymir/common/utils.py[85-104]
ymir/agents/backport_agent.py[577-585]
ymir/agents/backport_agent.py[1125-1133]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`run_build` catches `ToolError`, but `run_tool` raises from `next(...)` when the requested gateway tool is absent. Convert missing-tool lookup failures into a structured infrastructure failure without swallowing malformed build-result validation errors or cancellation.

## Issue Context
The deterministic build path now directly resolves `build_package` from the gateway's advertised tool list. An incomplete gateway tool set must follow existing workflow infrastructure-error routing rather than aborting the graph.

## Fix Focus Areas
- ymir/agents/build_agent.py[50-58]
- ymir/common/utils.py[85-104]
- ymir/agents/tests/unit/test_build_agent.py[97-109]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit 6923833 🧠 Deep

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Consolidated builds never reach Copr 🐞 Bug ≡ Correctness

Description

run_build_agent passes state.jira_issue directly into BuildInputSchema, even though
consolidation sets that value to None when the selected branches contain no Jira footers. The
deterministic call forwards the null value to build_package, whose input schema requires a string
Jira issue, so those consolidations exhaust build retries without submitting a Copr build.

Code

ymir/agents/mr_consolidation_agent.py[R782-787]

+                build_output = await run_build(
+                    build_input=BuildInputSchema(
+                        srpm_path=state.consolidation_result.srpm_path,
+                        dist_git_branch=dist_git_branch,
+                        jira_issue=state.jira_issue,
+                    ),

Relevance

●●● Strong
Null propagation into a required downstream build field is a concrete workflow failure; recent
history accepts defensive validation.
PR-#726
PR-#611

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The new call forwards state.jira_issue; consolidation explicitly assigns it to None if footer
collection yields no Jira keys, while the build tool declares jira_issue as a required str and
uses it as projectname for the Copr project.
ymir/agents/mr_consolidation_agent.py[690-707]
ymir/tools/privileged/copr.py[85-88]
ymir/tools/privileged/copr.py[142-148]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The deterministic consolidation build invocation can pass `None` as `jira_issue`, but the `build_package` tool requires a string and uses it as its Copr project name. This makes valid consolidations whose commits have no Jira footer fail before a build is submitted.

## Issue Context
`fork_and_prepare_dist_git` intentionally derives `state.jira_issue` from collected commit footers and leaves it unset when none exist. Preserve existing behavior for consolidations that do not have a Jira issue by deriving a valid stable build/project identifier or otherwise handling that case before calling the build tool.

## Fix Focus Areas
- ymir/agents/mr_consolidation_agent.py[782-789]
- ymir/tools/privileged/copr.py[85-88]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Failed builds lose log diagnosis 🐞 Bug ☼ Reliability

Description

create_build_failure_agent disables every local fallback whenever extract_log_snippets exists,
even when the required download_artifacts tool is absent. With that partial gateway tool set,
extraction is constrained to follow an unavailable download operation, so diagnosis cannot inspect
the Copr logs and retains only the generic build error.

Code

ymir/agents/build_agent.py[R176-179]

+    local_tools = (
+        []
+        if has_extract_log_snippets
+        else [

Relevance

●●● Strong
Partial gateway tool availability can strand diagnosis; accepted precedents favor defensive fallback
handling for missing optional data.
PR-#726
PR-#571

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The agent derives has_extract_log_snippets from the extractor alone, constrains that extractor to
run only after download_artifacts, and removes local tools whenever the extractor is present. The
prompt confirms that gateway-downloaded logs are accessible only through extraction, while gateway
registration shows the extractor is optional and separately sourced from the standard downloader.

ymir/agents/build_agent.py[155-185]
ymir/agents/prompts/build/instructions.j2[7-20]
ymir/tools/gateway_utils.py[73-86]
ymir/tools/privileged/gateway.py[104-117]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Failed-build diagnosis selects the gateway-only log path based solely on `extract_log_snippets`, although that tool cannot inspect Copr logs until `download_artifacts` has downloaded them. If only the extractor is advertised, the agent receives neither a usable gateway path nor the local URL-based fallback tools.

## Issue Context
Treat the gateway extraction path as available only when both `download_artifacts` and `extract_log_snippets` are present. Otherwise retain the local tools and render the fallback instructions; add coverage for the extractor-without-downloader combination.

## Fix Focus Areas
- ymir/agents/build_agent.py[155-185]
- ymir/agents/tests/unit/test_build_agent.py[401-421]
- ymir/agents/prompts/build/instructions.j2[7-20]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

nforro

Just curious, what was the motivation for this change?

opohorel · 2026-09-09T07:59:39Z

Just curious, what was the motivation for this change?

mainly to reduce token spend on a workflow, where LLM isn't that needed. thanks for the comments, I'll make the changes.

opohorel · 2026-09-09T12:41:42Z

/agentic_review

qodo-for-packit · 2026-09-09T12:44:44Z

Code review by qodo was updated up to the latest commit 6923833

opohorel · 2026-09-09T13:10:16Z

/agentic_review

qodo-for-packit · 2026-09-09T13:14:46Z

Code review by qodo was updated up to the latest commit 7d732f1

Call the existing build tool deterministically so successful builds no longer require model orchestration. Use a two-step BuildWorkflow and centralize opt-in typed result validation in run_tool. Migrate backport, inheritance, rebase, MR updates, and consolidation while preserving their timeout and retry policies. Keep rebuild and the incremental backport repair loop unchanged. Use a stable Copr project name for consolidations without Jira footers without changing Jira metadata. Require both gateway log tools for remote extraction; otherwise retrieve logs in a local temporary directory. Explicitly abort and drain the workflow on cancellation. Add regression tests for gateway decoding, zero-LLM success handling, error classification, cancellation, no-Jira consolidation retries, and all log-tool availability combinations. Document the shared build flow. Validation: make check-in-container passed with rebuilt test images (6 skipped tests), including the MCP installation smoke test. Ruff lint and format checks passed. Assisted-by: Codex

qodo-for-packit Bot reviewed Sep 8, 2026

View reviewed changes

Comment thread ymir/agents/build_agent.py Outdated

opohorel force-pushed the deterministic-build-execution branch from e911d1c to 4a1768d Compare September 8, 2026 15:11

nforro reviewed Sep 9, 2026

View reviewed changes

Comment thread ymir/agents/build_agent.py Outdated

Comment thread ymir/agents/build_agent.py

opohorel force-pushed the deterministic-build-execution branch from 4a1768d to 6923833 Compare September 9, 2026 12:41

qodo-for-packit Bot reviewed Sep 9, 2026

View reviewed changes

Comment thread ymir/agents/build_agent.py

Comment thread ymir/agents/mr_consolidation_agent.py

opohorel force-pushed the deterministic-build-execution branch from 6923833 to 7d732f1 Compare September 9, 2026 13:07

qodo-for-packit Bot reviewed Sep 9, 2026

View reviewed changes

Comment thread ymir/tools/privileged/copr.py

opohorel force-pushed the deterministic-build-execution branch from 7d732f1 to d595eb3 Compare September 9, 2026 13:37

opohorel requested a review from nforro September 9, 2026 13:52

Navigation Menu

Uh oh!

Run Copr builds directly and use LLMs only for diagnosis - #808

Run Copr builds directly and use LLMs only for diagnosis#808
opohorel wants to merge 1 commit into
packit:mainfrom
opohorel:deterministic-build-execution

opohorel commented Sep 8, 2026

Uh oh!

qodo-for-packit Bot commented Sep 8, 2026

Uh oh!

qodo-for-packit Bot commented Sep 8, 2026 •

edited

Loading

Uh oh!

Uh oh!

nforro left a comment

Uh oh!

Uh oh!

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

Uh oh!

Uh oh!

qodo-for-packit Bot commented Sep 9, 2026

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

Uh oh!

qodo-for-packit Bot commented Sep 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

opohorel commented Sep 8, 2026

Uh oh!

qodo-for-packit Bot commented Sep 8, 2026

PR Summary by Qodo

Uh oh!

qodo-for-packit Bot commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Uh oh!

Uh oh!

nforro left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

Uh oh!

Uh oh!

qodo-for-packit Bot commented Sep 9, 2026

Uh oh!

opohorel commented Sep 9, 2026

Uh oh!

Uh oh!

qodo-for-packit Bot commented Sep 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

qodo-for-packit Bot commented Sep 8, 2026 •

edited

Loading