OCPBUGS-69402: Ensure `InitLabel` only sets process label when unset #9666

bitoku · 2025-12-16T12:45:22Z

What type of PR is this?

/kind bug

What this PR does / why we need it:

When systemd runs in a container, process label will be container_init_t, even if a user specify selinux type explicitly.
This PR fixes the process label of systemd.

ref: #3754

Which issue(s) this PR fixes:

Special notes for your reviewer:

We need an image which can run systemd to write integration tests.

Does this PR introduce a user-facing change?

Respect user specified selinux label for systemd or init container.

Summary by CodeRabbit

Bug Fixes

Process label initialization in container creation now conditionally preserves pre-existing labels instead of unconditionally reinitializing them. The initialization only occurs when the label is empty, allowing existing labels to persist while maintaining error handling during container setup and system configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Signed-off-by: Ayato Tokubi <[email protected]>

openshift-ci-robot · 2025-12-16T12:45:28Z

@bitoku: This pull request references Jira Issue OCPBUGS-69402, which is invalid:

expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

When systemd runs in a container, process label will be container_init_t, even if a user specify selinux type explicitly.
This PR fixes the process label of systemd.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Respect user specified selinux label for systemd or init container. 

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2025-12-16T12:45:42Z

Walkthrough

A single conditional logic modification in server/container_create.go ensures that the process label initialization only occurs when the label is empty, preserving any pre-existing label value instead of unconditionally overwriting it.

Changes

Cohort / File(s)	Summary
Process label initialization `server/container_create.go`	Modified `setupContainerMountsAndSystemd` to conditionally invoke `InitLabel` only when `processLabel` is empty, preserving already-set labels while maintaining error handling

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3–5 minutes

Single file, single function affected
Straightforward conditional logic addition with no structural complexity
No method signature changes or cross-component impacts

Poem

🐰 A label once lost, now safely kept,
When empty alone, InitLabel's stepped.
No overwrites here, just gentle grace—
The process label finds its place! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: making InitLabel conditionally set the process label only when unset, which directly aligns with the code modification in setupContainerMountsAndSystemd.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci-robot · 2025-12-16T12:47:23Z

@bitoku: This pull request references Jira Issue OCPBUGS-69402, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

When systemd runs in a container, process label will be container_init_t, even if a user specify selinux type explicitly.
This PR fixes the process label of systemd.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Respect user specified selinux label for systemd or init container. 
Summary by CodeRabbit

Bug Fixes

Process label initialization in container creation now conditionally preserves pre-existing labels instead of unconditionally reinitializing them. The initialization only occurs when the label is empty, allowing existing labels to persist while maintaining error handling during container setup and system configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2025-12-16T12:47:27Z

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: lyman9966.

Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@bitoku: This pull request references Jira Issue OCPBUGS-69402, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)

bug target version (4.22.0) matches configured target version for branch (4.22.0)

bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966
In response to this:
What type of PR is this?

/kind bug

What this PR does / why we need it:

When systemd runs in a container, process label will be container_init_t, even if a user specify selinux type explicitly.
This PR fixes the process label of systemd.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?
Respect user specified selinux label for systemd or init container. 
Summary by CodeRabbit

Bug Fixes

Process label initialization in container creation now conditionally preserves pre-existing labels instead of unconditionally reinitializing them. The initialization only occurs when the label is empty, allowing existing labels to persist while maintaining error handling during container setup and system configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

bitoku · 2025-12-16T12:47:31Z

/jira refresh

openshift-ci-robot · 2025-12-16T12:47:35Z

@bitoku: This pull request references Jira Issue OCPBUGS-69402, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2025-12-16T12:47:39Z

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: lyman9966.

Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@bitoku: This pull request references Jira Issue OCPBUGS-69402, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)

bug target version (4.22.0) matches configured target version for branch (4.22.0)

bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lyman9966

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

codecov · 2025-12-16T12:55:56Z

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 67.10%. Comparing base (2e590ab) to head (4e2f7db).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9666      +/-   ##
==========================================
- Coverage   67.28%   67.10%   -0.18%     
==========================================
  Files         208      208              
  Lines       28983    28987       +4     
==========================================
- Hits        19500    19452      -48     
- Misses       7819     7876      +57     
+ Partials     1664     1659       -5

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

haircommander · 2025-12-16T14:22:47Z

/lgtm
/approve

I'm not sure what's up with CI, but it's very natural for it to break the week of a cri-o release :)

openshift-ci · 2025-12-16T14:22:56Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bitoku, haircommander

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [haircommander]

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

haircommander · 2025-12-16T18:01:12Z

/retest

openshift-ci-robot · 2025-12-16T23:47:23Z

@bitoku: Jira Issue OCPBUGS-69402: All pull requests linked via external trackers have merged:

cri-o/cri-o#9666

Jira Issue OCPBUGS-69402 has been moved to the MODIFIED state.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

When systemd runs in a container, process label will be container_init_t, even if a user specify selinux type explicitly.
This PR fixes the process label of systemd.

ref: #3754

Which issue(s) this PR fixes:

Special notes for your reviewer:

We need an image which can run systemd to write integration tests.

Does this PR introduce a user-facing change?
Respect user specified selinux label for systemd or init container. 
Summary by CodeRabbit

Bug Fixes

Process label initialization in container creation now conditionally preserves pre-existing labels instead of unconditionally reinitializing them. The initialization only occurs when the label is empty, allowing existing labels to persist while maintaining error handling during container setup and system configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

bitoku · 2025-12-17T11:58:08Z

/jira backport release-4.21

openshift-ci-robot · 2025-12-17T11:58:22Z

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21

Details

In response to this:

/jira backport release-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-cherrypick-robot · 2025-12-17T11:59:02Z

@openshift-ci-robot: cannot checkout release-4.21: error checking out "release-4.21": exit status 1 error: pathspec 'release-4.21' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21

In response to this:

/jira backport release-4.21

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

bitoku · 2025-12-17T12:00:00Z

/cherry-pick release-1.34

openshift-cherrypick-robot · 2025-12-17T12:00:42Z

@bitoku: #9666 failed to apply on top of branch "release-1.34":

Applying: Ensure `InitLabel` only sets process label when unset
Using index info to reconstruct a base tree...
M	server/container_create.go
Falling back to patching base and 3-way merge...
Auto-merging server/container_create.go
CONFLICT (content): Merge conflict in server/container_create.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Ensure `InitLabel` only sets process label when unset

Details

In response to this:

/cherry-pick release-1.34

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

bitoku · 2025-12-17T12:14:58Z

/jira backport release-4.20,release-4.19,release-4.18,release-4.17

openshift-ci-robot · 2025-12-17T12:15:01Z

@bitoku: Missing required branches for backport chain:

openshift-4.21 OR release-4.21,

Details

In response to this:

/jira backport release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

bitoku · 2025-12-17T12:15:12Z

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

openshift-ci-robot · 2025-12-17T12:15:49Z

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21
OCPBUGS-69670 for branch release-4.20
OCPBUGS-69671 for branch release-4.19
OCPBUGS-69672 for branch release-4.18
OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

Details

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-cherrypick-robot · 2025-12-17T12:16:28Z

@openshift-ci-robot: cannot checkout release-4.17: error checking out "release-4.17": exit status 1 error: pathspec 'release-4.17' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

OCPBUGS-69670 for branch release-4.20

OCPBUGS-69671 for branch release-4.19

OCPBUGS-69672 for branch release-4.18

OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-cherrypick-robot · 2025-12-17T12:17:05Z

@openshift-ci-robot: cannot checkout release-4.18: error checking out "release-4.18": exit status 1 error: pathspec 'release-4.18' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

OCPBUGS-69670 for branch release-4.20

OCPBUGS-69671 for branch release-4.19

OCPBUGS-69672 for branch release-4.18

OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-cherrypick-robot · 2025-12-17T12:17:44Z

@openshift-ci-robot: cannot checkout release-4.19: error checking out "release-4.19": exit status 1 error: pathspec 'release-4.19' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

OCPBUGS-69670 for branch release-4.20

OCPBUGS-69671 for branch release-4.19

OCPBUGS-69672 for branch release-4.18

OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-cherrypick-robot · 2025-12-17T12:18:22Z

@openshift-ci-robot: cannot checkout release-4.20: error checking out "release-4.20": exit status 1 error: pathspec 'release-4.20' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

OCPBUGS-69670 for branch release-4.20

OCPBUGS-69671 for branch release-4.19

OCPBUGS-69672 for branch release-4.18

OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-cherrypick-robot · 2025-12-17T12:18:59Z

@openshift-ci-robot: cannot checkout release-4.21: error checking out "release-4.21": exit status 1 error: pathspec 'release-4.21' did not match any file(s) known to git

Details

In response to this:

@bitoku: The following backport issues have been created:

OCPBUGS-69669 for branch release-4.21

OCPBUGS-69670 for branch release-4.20

OCPBUGS-69671 for branch release-4.19

OCPBUGS-69672 for branch release-4.18

OCPBUGS-69673 for branch release-4.17

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.21
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17

In response to this:

/jira backport release-4.21,release-4.20,release-4.19,release-4.18,release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Ensure InitLabel only sets process label when unset

4e2f7db

Signed-off-by: Ayato Tokubi <[email protected]>

bitoku requested a review from mrunalp as a code owner December 16, 2025 12:45

openshift-ci bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Dec 16, 2025

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Dec 16, 2025

openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 16, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 16, 2025

openshift-ci bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Dec 16, 2025

openshift-ci bot requested review from hasan4791 and littlejawa December 16, 2025 12:45

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 16, 2025

openshift-ci bot assigned haircommander Dec 16, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 16, 2025

openshift-merge-bot bot merged commit 0e42a1f into cri-o:main Dec 16, 2025
69 of 71 checks passed

bitoku mentioned this pull request Dec 17, 2025

OCPBUGS-69669: [release-1.34] Ensure InitLabel only sets process label when unset #9671

Merged

coderabbitai bot mentioned this pull request Dec 17, 2025

Refactor mount and selinux codes in container creation. #9667

Open

OCPBUGS-69402: Ensure InitLabel only sets process label when unset #9666

OCPBUGS-69402: Ensure InitLabel only sets process label when unset #9666

Uh oh!

Conversation

bitoku commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Summary by CodeRabbit

Bug Fixes

Uh oh!

openshift-ci-robot commented Dec 16, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Uh oh!

coderabbitai bot commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Pre-merge checks and finishing touches

Uh oh!

openshift-ci-robot commented Dec 16, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Summary by CodeRabbit

Bug Fixes

Uh oh!

openshift-ci bot commented Dec 16, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Summary by CodeRabbit

Bug Fixes

Uh oh!

bitoku commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

openshift-ci bot commented Dec 16, 2025

Uh oh!

codecov bot commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

haircommander commented Dec 16, 2025

Uh oh!

openshift-ci bot commented Dec 16, 2025

Uh oh!

haircommander commented Dec 16, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 16, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Summary by CodeRabbit

Bug Fixes

Uh oh!

bitoku commented Dec 17, 2025

Uh oh!

openshift-ci-robot commented Dec 17, 2025

Uh oh!

openshift-cherrypick-robot commented Dec 17, 2025

Uh oh!

bitoku commented Dec 17, 2025

OCPBUGS-69402: Ensure `InitLabel` only sets process label when unset #9666

OCPBUGS-69402: Ensure `InitLabel` only sets process label when unset #9666

bitoku commented Dec 16, 2025 •

edited

Loading

coderabbitai bot commented Dec 16, 2025 •

edited

Loading

codecov bot commented Dec 16, 2025 •

edited

Loading