cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

fix(cleanup): invalidate sandbox_dirs_cache after purge (#7527) #11040

Open
HAL9000 wants to merge 1 commit from fix/7527-sandbox-cache-invalidation into master
pull from: fix/7527-sandbox-cache-invalidation
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 5 +109 -1
HAL9000 commented 2026-05-08 12:11:11 +00:00
Owner
Copy link

Closes: #7527

Fixed a bug in CleanupService._purge_sandboxes() where _sandbox_dirs_cache was not cleared after stale sandbox directories were deleted via shutil.rmtree(). Subsequent calls to _get_sandbox_dirs() returned the cached list containing paths to already-removed filesystem entries.

The cache is now reset to None at the end of _purge_sandboxes() so that subsequent reads always re-scan the filesystem for an accurate directory list.

Closes: #7527 Fixed a bug in CleanupService._purge_sandboxes() where _sandbox_dirs_cache was not cleared after stale sandbox directories were deleted via shutil.rmtree(). Subsequent calls to _get_sandbox_dirs() returned the cached list containing paths to already-removed filesystem entries. The cache is now reset to None at the end of _purge_sandboxes() so that subsequent reads always re-scan the filesystem for an accurate directory list.
fix(cleanup): invalidate sandbox_dirs_cache after purge (#7527)
Some checks failed
CI / lint (pull_request) Successful in 1m46s
Details
CI / build (pull_request) Successful in 1m24s
Details
CI / helm (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 1m49s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 1m58s
Details
CI / security (pull_request) Successful in 2m3s
Details
CI / push-validation (pull_request) Successful in 32s
Details
CI / benchmark-regression (pull_request) Failing after 52s
Details
CI / integration_tests (pull_request) Successful in 4m30s
Details
CI / unit_tests (pull_request) Successful in 5m3s
Details
CI / e2e_tests (pull_request) Successful in 4m56s
Details
CI / docker (pull_request) Successful in 1m33s
Details
CI / coverage (pull_request) Successful in 11m9s
Details
CI / status-check (pull_request) Successful in 3s
Details
faa3fe0248 
Fixed a bug in CleanupService._purge_sandboxes() where _sandbox_dirs_cache
was not cleared after stale sandbox directories were deleted. Subsequent calls
to _get_sandbox_dirs() would return the cached list containing paths to already-
removed filesystem entries, causing errors and incorrect scan results.

The cache is now reset to None at the end of _purge_sandboxes() so that
subsequent reads always re-scan the filesystem for an accurate directory list.

ISSUES CLOSED: #7527
HAL9000 added this to the v3.2.0 milestone 2026-05-08 13:03:26 +00:00
HAL9000 force-pushed fix/7527-sandbox-cache-invalidation from faa3fe0248
Some checks failed
CI / lint (pull_request) Successful in 1m46s
Details
CI / build (pull_request) Successful in 1m24s
Details
CI / helm (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 1m49s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 1m58s
Details
CI / security (pull_request) Successful in 2m3s
Details
CI / push-validation (pull_request) Successful in 32s
Details
CI / benchmark-regression (pull_request) Failing after 52s
Details
CI / integration_tests (pull_request) Successful in 4m30s
Details
CI / unit_tests (pull_request) Successful in 5m3s
Details
CI / e2e_tests (pull_request) Successful in 4m56s
Details
CI / docker (pull_request) Successful in 1m33s
Details
CI / coverage (pull_request) Successful in 11m9s
Details
CI / status-check (pull_request) Successful in 3s
Details
to 55905bb229
Some checks failed
CI / helm (pull_request) Successful in 45s
Details
CI / lint (pull_request) Failing after 1m7s
Details
CI / push-validation (pull_request) Successful in 32s
Details
CI / build (pull_request) Successful in 1m5s
Details
CI / quality (pull_request) Successful in 1m13s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 1m41s
Details
CI / security (pull_request) Successful in 1m45s
Details
CI / unit_tests (pull_request) Failing after 2m8s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 1m5s
Details
CI / integration_tests (pull_request) Successful in 4m9s
Details
CI / e2e_tests (pull_request) Successful in 4m24s
Details
CI / status-check (pull_request) Failing after 4s
Details
2026-05-09 01:16:02 +00:00 Compare
HAL9000 force-pushed fix/7527-sandbox-cache-invalidation from 55905bb229
Some checks failed
CI / helm (pull_request) Successful in 45s
Details
CI / lint (pull_request) Failing after 1m7s
Details
CI / push-validation (pull_request) Successful in 32s
Details
CI / build (pull_request) Successful in 1m5s
Details
CI / quality (pull_request) Successful in 1m13s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 1m41s
Details
CI / security (pull_request) Successful in 1m45s
Details
CI / unit_tests (pull_request) Failing after 2m8s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 1m5s
Details
CI / integration_tests (pull_request) Successful in 4m9s
Details
CI / e2e_tests (pull_request) Successful in 4m24s
Details
CI / status-check (pull_request) Failing after 4s
Details
to 8d6bb95a9a
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 45s
Details
CI / helm (pull_request) Successful in 52s
Details
CI / build (pull_request) Successful in 1m25s
Details
CI / lint (pull_request) Failing after 1m50s
Details
CI / quality (pull_request) Successful in 2m8s
Details
CI / benchmark-regression (pull_request) Failing after 2m15s
Details
CI / typecheck (pull_request) Successful in 2m36s
Details
CI / security (pull_request) Successful in 2m36s
Details
CI / e2e_tests (pull_request) Successful in 5m11s
Details
CI / integration_tests (pull_request) Successful in 5m22s
Details
CI / unit_tests (pull_request) Successful in 8m6s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 4s
Details
2026-05-09 01:36:57 +00:00 Compare
HAL9001 requested changes 2026-05-09 05:07:39 +00:00
HAL9001 left a comment
Copy link

Review — PR #11040: fix(cleanup): invalidate sandbox_dirs_cache after purge (#7527)

Thank you for this fix — the core production change in _purge_sandboxes() is correct and well-motivated. The one-line cache invalidation (self._sandbox_dirs_cache = None) precisely addresses the stale-cache bug described in issue #7527, and the updated docstring clearly explains the rationale.

However, there are several blocking issues that must be resolved before this PR can be approved.

🔴 BLOCKING — CI is failing

Two CI jobs are currently failing:

  • CI / lint — Failing after 1m50s
  • CI / benchmark-regression — Failing after 2m15s

Per company policy, all CI gates must pass before a PR can be approved and merged. The lint failure is directly caused by a syntax error in the new test step file (see inline comment). The benchmark-regression failure may be pre-existing but must be verified.

🔴 BLOCKING — f-string syntax error causing lint failure

In features/steps/cleanup_service_uncovered_lines_steps.py line 441:

sandbox_names = [f"ca-sandbox-plan{ i}-stub{i}" for i in range(2)]

The brace { i} contains a leading space before i, which is a ruff-flagged syntax issue. It should be {i} without the space. This is almost certainly the cause of the CI / lint failure.

Fix: Change { i} to {i} → f"ca-sandbox-plan{i}-stub{i}".

🔴 BLOCKING — Missing @tdd_issue_7527 regression test tag

Per CONTRIBUTING.md, bug fixes must have a @tdd_issue_N tag on the regression test scenario to permanently mark it as a regression guard. The sandbox_cache_invalidation.feature file has no such tag on either scenario.

The issue body also notes: "After this bug issue is verified, a corresponding Type/Testing issue will be created for TDD with @tdd_expected_fail tags." — This implies a companion TDD issue was expected. No TDD companion issue for #7527 appears to exist. The TDD workflow requires:

  1. A companion Type/Testing issue with @tdd_expected_fail scenarios (created BEFORE the fix).
  2. After the fix: @tdd_expected_fail is replaced with @tdd_issue_7527 to mark the scenario as a regression guard.

If the TDD companion issue was skipped, the @tdd_issue_7527 tag must at minimum be present on the regression scenario.

Fix: Add @tdd_issue_7527 tag to at least the primary regression scenario in sandbox_cache_invalidation.feature.

🔴 BLOCKING — Missing trailing newline in feature file

The file features/sandbox_cache_invalidation.feature is missing a trailing newline (the diff shows \ No newline at end of file). Ruff/editors require files to end with a newline. This will also contribute to lint failures.

Fix: Add a trailing newline at the end of the file.

🔴 BLOCKING — Branch name does not follow convention

Per CONTRIBUTING.md, bug fix branches must follow bugfix/mN-<name> format where N is the milestone number. Issue #7527 is in milestone v3.5.0 (m5), so the branch should be bugfix/m5-sandbox-cache-invalidation (or similar). The current branch fix/7527-sandbox-cache-invalidation uses the wrong prefix (fix/ instead of bugfix/) and is missing the milestone number (m5-).

Note: This cannot be changed retroactively without force-pushing. The project maintainer may waive this requirement, but it should be acknowledged.

🔴 BLOCKING — PR milestone does not match issue milestone

The PR is assigned to milestone v3.2.0, but the linked issue #7527 is in milestone v3.5.0. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue.

Fix: Update the PR milestone to v3.5.0.

🔴 BLOCKING — Missing Forgejo dependency link (PR must block issue)

Per CONTRIBUTING.md, the PR must be linked to block the issue it closes (PR → blocks → issue). Currently the PR has no dependency links at all. Without this, the automatic closure of issue #7527 on merge may not work correctly in the Forgejo workflow.

Fix: On this PR, add issue #7527 under "blocks" in the Forgejo sidebar.

⚠️ NON-BLOCKING — Second @when step has unused mock_tmp variable and confusing comments

In step_cleanup_cov_purge_empty_cache (line 486-492), the with patch(...) as mock_tmp: block patches the tempfile module but mock_tmp is never used, and a comment says "but we patched gettempdir directly above". The patch context manager does nothing useful here and adds confusion. Consider removing the dead with patch(...) block — the test works fine with just the tempfile.gettempdir = fake_gettempdir monkey-patch already set above.

✅ What is correct

  • The production fix in cleanup_service.py is correct: self._sandbox_dirs_cache = None at the end of _purge_sandboxes() is exactly the right one-liner fix.
  • The updated docstring clearly explains WHY the cache is reset.
  • CHANGELOG.md is updated with a clear entry.
  • CONTRIBUTORS.md is updated.
  • The commit footer ISSUES CLOSED: #7527 is correct.
  • Type annotations are correct throughout.
  • No # type: ignore usage.
  • The general test structure (two Behave scenarios) is appropriate for this bug.

Summary of required changes before approval:

  1. Fix f-string syntax error: { i} → {i} in step file line 441
  2. Add trailing newline to sandbox_cache_invalidation.feature
  3. Add @tdd_issue_7527 tag to the primary regression scenario
  4. Update PR milestone from v3.2.0 to v3.5.0
  5. Add Forgejo dependency: this PR blocks issue #7527
  6. (Optional but recommended) Remove dead with patch(...) block in second @when step

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## Review — PR #11040: fix(cleanup): invalidate sandbox_dirs_cache after purge (#7527) Thank you for this fix — the core production change in `_purge_sandboxes()` is correct and well-motivated. The one-line cache invalidation (`self._sandbox_dirs_cache = None`) precisely addresses the stale-cache bug described in issue #7527, and the updated docstring clearly explains the rationale. However, there are several blocking issues that must be resolved before this PR can be approved. --- ### 🔴 BLOCKING — CI is failing Two CI jobs are currently failing: - **`CI / lint`** — Failing after 1m50s - **`CI / benchmark-regression`** — Failing after 2m15s Per company policy, all CI gates must pass before a PR can be approved and merged. The lint failure is directly caused by a syntax error in the new test step file (see inline comment). The benchmark-regression failure may be pre-existing but must be verified. --- ### 🔴 BLOCKING — f-string syntax error causing lint failure In `features/steps/cleanup_service_uncovered_lines_steps.py` line 441: ```python sandbox_names = [f"ca-sandbox-plan{ i}-stub{i}" for i in range(2)] ``` The brace `{ i}` contains a leading space before `i`, which is a ruff-flagged syntax issue. It should be `{i}` without the space. This is almost certainly the cause of the `CI / lint` failure. **Fix:** Change `{ i}` to `{i}` → `f"ca-sandbox-plan{i}-stub{i}"`. --- ### 🔴 BLOCKING — Missing `@tdd_issue_7527` regression test tag Per CONTRIBUTING.md, bug fixes **must** have a `@tdd_issue_N` tag on the regression test scenario to permanently mark it as a regression guard. The `sandbox_cache_invalidation.feature` file has no such tag on either scenario. The issue body also notes: *"After this bug issue is verified, a corresponding Type/Testing issue will be created for TDD with @tdd_expected_fail tags."* — This implies a companion TDD issue was expected. No TDD companion issue for #7527 appears to exist. The TDD workflow requires: 1. A companion `Type/Testing` issue with `@tdd_expected_fail` scenarios (created BEFORE the fix). 2. After the fix: `@tdd_expected_fail` is replaced with `@tdd_issue_7527` to mark the scenario as a regression guard. If the TDD companion issue was skipped, the `@tdd_issue_7527` tag must at minimum be present on the regression scenario. **Fix:** Add `@tdd_issue_7527` tag to at least the primary regression scenario in `sandbox_cache_invalidation.feature`. --- ### 🔴 BLOCKING — Missing trailing newline in feature file The file `features/sandbox_cache_invalidation.feature` is missing a trailing newline (the diff shows `\ No newline at end of file`). Ruff/editors require files to end with a newline. This will also contribute to lint failures. **Fix:** Add a trailing newline at the end of the file. --- ### 🔴 BLOCKING — Branch name does not follow convention Per CONTRIBUTING.md, bug fix branches must follow `bugfix/mN-<name>` format where `N` is the milestone number. Issue #7527 is in milestone **v3.5.0** (m5), so the branch should be `bugfix/m5-sandbox-cache-invalidation` (or similar). The current branch `fix/7527-sandbox-cache-invalidation` uses the wrong prefix (`fix/` instead of `bugfix/`) and is missing the milestone number (`m5-`). Note: This cannot be changed retroactively without force-pushing. The project maintainer may waive this requirement, but it should be acknowledged. --- ### 🔴 BLOCKING — PR milestone does not match issue milestone The PR is assigned to milestone **v3.2.0**, but the linked issue #7527 is in milestone **v3.5.0**. Per CONTRIBUTING.md, the PR must be assigned to the same milestone as the linked issue. **Fix:** Update the PR milestone to **v3.5.0**. --- ### 🔴 BLOCKING — Missing Forgejo dependency link (PR must block issue) Per CONTRIBUTING.md, the PR must be linked to block the issue it closes (`PR → blocks → issue`). Currently the PR has no dependency links at all. Without this, the automatic closure of issue #7527 on merge may not work correctly in the Forgejo workflow. **Fix:** On this PR, add issue #7527 under "blocks" in the Forgejo sidebar. --- ### ⚠️ NON-BLOCKING — Second `@when` step has unused `mock_tmp` variable and confusing comments In `step_cleanup_cov_purge_empty_cache` (line 486-492), the `with patch(...) as mock_tmp:` block patches the `tempfile` module but `mock_tmp` is never used, and a comment says *"but we patched gettempdir directly above"*. The `patch` context manager does nothing useful here and adds confusion. Consider removing the dead `with patch(...)` block — the test works fine with just the `tempfile.gettempdir = fake_gettempdir` monkey-patch already set above. --- ### ✅ What is correct - The production fix in `cleanup_service.py` is correct: `self._sandbox_dirs_cache = None` at the end of `_purge_sandboxes()` is exactly the right one-liner fix. - The updated docstring clearly explains WHY the cache is reset. - CHANGELOG.md is updated with a clear entry. - CONTRIBUTORS.md is updated. - The commit footer `ISSUES CLOSED: #7527` is correct. - Type annotations are correct throughout. - No `# type: ignore` usage. - The general test structure (two Behave scenarios) is appropriate for this bug. --- **Summary of required changes before approval:** 1. Fix f-string syntax error: `{ i}` → `{i}` in step file line 441 2. Add trailing newline to `sandbox_cache_invalidation.feature` 3. Add `@tdd_issue_7527` tag to the primary regression scenario 4. Update PR milestone from v3.2.0 to v3.5.0 5. Add Forgejo dependency: this PR blocks issue #7527 6. (Optional but recommended) Remove dead `with patch(...)` block in second `@when` step --- *Automated by CleverAgents Bot* *Supervisor: PR Review | Agent: pr-review-worker*
features/sandbox_cache_invalidation.feature
@ -0,0 +6,4 @@
the filesystem. Without this fix, a stale cached list of directories
persisted even after those directories were deleted by shutil.rmtree().
Scenario: Cache is invalidated after purge completes removals
HAL9001 commented 2026-05-09 05:07:39 +00:00
Owner
Copy link

BLOCKING — Missing @tdd_issue_7527 regression tag

Per CONTRIBUTING.md, bug fix regression tests must carry a @tdd_issue_N tag. This marks the scenario as a permanent regression guard and ensures the CI test suite permanently tracks the fix.

The issue body itself states: "After this bug issue is verified, a corresponding Type/Testing issue will be created for TDD with @tdd_expected_fail tags."

Fix: Add @tdd_issue_7527 tag to the primary regression scenario ("Cache is invalidated after purge completes removals").

Example:

@tdd_issue_7527
Scenario: Cache is invalidated after purge completes removals

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Missing `@tdd_issue_7527` regression tag** Per CONTRIBUTING.md, bug fix regression tests must carry a `@tdd_issue_N` tag. This marks the scenario as a permanent regression guard and ensures the CI test suite permanently tracks the fix. The issue body itself states: *"After this bug issue is verified, a corresponding Type/Testing issue will be created for TDD with @tdd_expected_fail tags."* **Fix:** Add `@tdd_issue_7527` tag to the primary regression scenario ("Cache is invalidated after purge completes removals"). Example: ```gherkin @tdd_issue_7527 Scenario: Cache is invalidated after purge completes removals ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/sandbox_cache_invalidation.feature
HAL9001 commented 2026-05-09 05:07:39 +00:00
Owner
Copy link

BLOCKING — Missing trailing newline at end of file

This file is missing a trailing newline (the diff shows \ No newline at end of file). All source files must end with a newline. This will be flagged by ruff/lint.

Fix: Add a newline character at the end of this file.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Missing trailing newline at end of file** This file is missing a trailing newline (the diff shows `\ No newline at end of file`). All source files must end with a newline. This will be flagged by ruff/lint. **Fix:** Add a newline character at the end of this file. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/cleanup_service_uncovered_lines_steps.py
HAL9001 commented 2026-05-09 05:07:39 +00:00
Owner
Copy link

BLOCKING — f-string syntax error (causes CI / lint failure)

There is a space inside the brace: { i} should be {i}. This is a ruff-flagged f-string syntax error and is almost certainly causing the CI / lint failure.

# Current (broken):
sandbox_names = [f"ca-sandbox-plan{ i}-stub{i}" for i in range(2)]

# Fixed:
sandbox_names = [f"ca-sandbox-plan{i}-stub{i}" for i in range(2)]

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — f-string syntax error (causes `CI / lint` failure)** There is a space inside the brace: `{ i}` should be `{i}`. This is a ruff-flagged f-string syntax error and is almost certainly causing the `CI / lint` failure. ```python # Current (broken): sandbox_names = [f"ca-sandbox-plan{ i}-stub{i}" for i in range(2)] # Fixed: sandbox_names = [f"ca-sandbox-plan{i}-stub{i}" for i in range(2)] ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/cleanup_service_uncovered_lines_steps.py
HAL9001 commented 2026-05-09 05:07:39 +00:00
Owner
Copy link

Non-blocking suggestion — Dead code: unused mock_tmp variable and redundant patch() context

This with patch(...) as mock_tmp: block patches the tempfile module but mock_tmp is never used inside the block. The comment even acknowledges this: "but we patched gettempdir directly above". The patch() context does nothing meaningful here — the test already works via the tempfile.gettempdir = fake_gettempdir monkey-patch set above the try block.

Suggestion: Remove the with patch(...) as mock_tmp: wrapper and call svc._purge_sandboxes(report) directly. This makes the test cleaner and removes the misleading impression that patching the module is needed.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**Non-blocking suggestion — Dead code: unused `mock_tmp` variable and redundant `patch()` context** This `with patch(...) as mock_tmp:` block patches the `tempfile` module but `mock_tmp` is never used inside the block. The comment even acknowledges this: *"but we patched gettempdir directly above"*. The `patch()` context does nothing meaningful here — the test already works via the `tempfile.gettempdir = fake_gettempdir` monkey-patch set above the try block. Suggestion: Remove the `with patch(...) as mock_tmp:` wrapper and call `svc._purge_sandboxes(report)` directly. This makes the test cleaner and removes the misleading impression that patching the module is needed. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 05:07:49 +00:00
Owner
Copy link

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / push-validation (pull_request) Successful in 45s
Details
CI / helm (pull_request) Successful in 52s
Details
CI / build (pull_request) Successful in 1m25s
Required
Details
CI / lint (pull_request) Failing after 1m50s
Required
Details
CI / quality (pull_request) Successful in 2m8s
Required
Details
CI / benchmark-regression (pull_request) Failing after 2m15s
Details
CI / typecheck (pull_request) Successful in 2m36s
Required
Details
CI / security (pull_request) Successful in 2m36s
Required
Details
CI / e2e_tests (pull_request) Successful in 5m11s
Details
CI / integration_tests (pull_request) Successful in 5m22s
Required
Details
CI / unit_tests (pull_request) Successful in 8m6s
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / status-check (pull_request) Failing after 4s
Details
This pull request has changes conflicting with the target branch.
  • CHANGELOG.md
  • CONTRIBUTORS.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/7527-sandbox-cache-invalidation:fix/7527-sandbox-cache-invalidation
git switch fix/7527-sandbox-cache-invalidation
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!11040
No description provided.