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

fix(actor): move namespace filter inside lock in ActorLoader.list_actors (#8660) #11062

Open
HAL9000 wants to merge 1 commit from cleveragents-pr-fix-11038 into master
pull from: cleveragents-pr-fix-11038
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 1 +3 -4
HAL9000 commented 2026-05-08 22:54:36 +00:00
Owner
Copy link

The list_actors method previously acquired the lock to copy the actors dict into a list, then released the lock before applying the namespace filter. This created a race condition where another thread could modify self._actors between releasing the lock and filtering.

This fix moves the namespace filter logic inside the critical section/lock block, ensuring atomicity — the snapshot used for filtering is always consistent.

Relates to issue #8660.

The `list_actors` method previously acquired the lock to copy the actors dict into a list, then released the lock before applying the namespace filter. This created a race condition where another thread could modify `self._actors` between releasing the lock and filtering. This fix moves the namespace filter logic inside the critical section/lock block, ensuring atomicity — the snapshot used for filtering is always consistent. Relates to issue #8660.
fix(actor): move namespace filter inside lock in ActorLoader.list_actors
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 1m6s
Details
CI / build (pull_request) Successful in 46s
Details
CI / typecheck (pull_request) Successful in 1m47s
Details
CI / benchmark-regression (pull_request) Failing after 1m17s
Details
CI / push-validation (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 2m0s
Details
CI / security (pull_request) Successful in 2m6s
Details
CI / helm (pull_request) Successful in 1m0s
Details
CI / e2e_tests (pull_request) Successful in 4m8s
Details
CI / integration_tests (pull_request) Successful in 4m11s
Details
CI / unit_tests (pull_request) Successful in 6m45s
Details
CI / docker (pull_request) Successful in 2m6s
Details
CI / coverage (pull_request) Successful in 11m58s
Details
CI / status-check (pull_request) Successful in 3s
Details
b5f1712333 
The list_actors method previously acquired the lock to copy the actors dict into a list, then released the lock before applying the namespace filter. This created a race condition where another thread could modify self._actors between releasing the lock and filtering. Moving the namespace filter inside the lock ensures atomicity — the snapshot used for filtering is consistent.
HAL9001 requested changes 2026-05-09 05:07:59 +00:00
HAL9001 left a comment
Copy link

Review Summary

The core code change in this PR is correct — moving the namespace filter inside the with self._lock: block in ActorLoader.list_actors() does eliminate the TOCTOU race condition described in issue #8588. The one-line structural fix is clean, precise, and immediately understandable.

However, several blocking issues must be addressed before this PR can be approved:

  1. Missing concurrency regression test — Issue #8588 explicitly requires a new unit test exercising concurrent list_actors + clear()/discover() calls. No such test is present in this PR.
  2. No TDD companion issue — For bug fixes, CONTRIBUTING.md mandates a Type/Testing TDD issue (TDD: <bug description>) that must exist and the bug fix PR must depend on it. No TDD issue was created for #8588.
  3. No CHANGELOG entry — CONTRIBUTING.md requires one CHANGELOG entry per commit. The commit does not update CHANGELOG.md.
  4. Commit footer missing ISSUES CLOSED: — The commit body omits the required ISSUES CLOSED: #8588 footer.
  5. No CONTRIBUTORS.md update — First-contribution rule requires updating CONTRIBUTORS.md.
  6. PR metadata incomplete — No Type/ label, no milestone (v3.2.0), and no Forgejo dependency link (PR should block issue #8588, not reference it with "Relates to").
  7. Incorrect issue reference — The PR body says "Relates to issue #8660" using a weak reference. CONTRIBUTING.md requires Closes #N or Fixes #N, and the primary issue to close is #8588 (the original bug report), not #8660.

See inline comments for the details on each blocking item.

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

## Review Summary The core code change in this PR is **correct** — moving the namespace filter inside the `with self._lock:` block in `ActorLoader.list_actors()` does eliminate the TOCTOU race condition described in issue #8588. The one-line structural fix is clean, precise, and immediately understandable. However, several **blocking issues** must be addressed before this PR can be approved: 1. **Missing concurrency regression test** — Issue #8588 explicitly requires a new unit test exercising concurrent `list_actors` + `clear()`/`discover()` calls. No such test is present in this PR. 2. **No TDD companion issue** — For bug fixes, CONTRIBUTING.md mandates a `Type/Testing` TDD issue (`TDD: <bug description>`) that must exist and the bug fix PR must depend on it. No TDD issue was created for #8588. 3. **No CHANGELOG entry** — CONTRIBUTING.md requires one CHANGELOG entry per commit. The commit does not update `CHANGELOG.md`. 4. **Commit footer missing `ISSUES CLOSED:`** — The commit body omits the required `ISSUES CLOSED: #8588` footer. 5. **No `CONTRIBUTORS.md` update** — First-contribution rule requires updating `CONTRIBUTORS.md`. 6. **PR metadata incomplete** — No `Type/` label, no milestone (`v3.2.0`), and no Forgejo dependency link (PR should block issue #8588, not reference it with "Relates to"). 7. **Incorrect issue reference** — The PR body says "Relates to issue #8660" using a weak reference. CONTRIBUTING.md requires `Closes #N` or `Fixes #N`, and the primary issue to close is #8588 (the original bug report), not #8660. See inline comments for the details on each blocking item. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
src/cleveragents/actor/loader.py
HAL9001 commented 2026-05-09 05:07:59 +00:00
Owner
Copy link

BLOCKING — Missing concurrency regression test

The code change here is correct: the namespace filter is now inside the lock, making the read-and-filter operation atomic.

However, issue #8588 acceptance criteria explicitly require:

"A new unit test is added that exercises concurrent list_actors + clear()/discover() calls to verify no stale data is returned"

No such test is present in this PR. Without a concurrency regression test, this fix is unverifiable and the race condition could silently regress. WHY this is blocking: bug fixes require a @tdd_issue_N regression test that proves the bug existed before the fix and passes after. HOW to fix: add a Behave scenario in features/actor_loading.feature (or a new features/actor_loader_concurrency.feature) with a step that spawns two threads — one calling list_actors(namespace=...) and one calling clear() simultaneously — and asserts no exception and consistent results. The step implementation goes in features/steps/actor_loading_steps.py.

**BLOCKING — Missing concurrency regression test** The code change here is correct: the namespace filter is now inside the lock, making the read-and-filter operation atomic. However, issue #8588 acceptance criteria explicitly require: > "A new unit test is added that exercises concurrent `list_actors` + `clear()`/`discover()` calls to verify no stale data is returned" No such test is present in this PR. Without a concurrency regression test, this fix is unverifiable and the race condition could silently regress. WHY this is blocking: bug fixes require a `@tdd_issue_N` regression test that proves the bug existed before the fix and passes after. HOW to fix: add a Behave scenario in `features/actor_loading.feature` (or a new `features/actor_loader_concurrency.feature`) with a step that spawns two threads — one calling `list_actors(namespace=...)` and one calling `clear()` simultaneously — and asserts no exception and consistent results. The step implementation goes in `features/steps/actor_loading_steps.py`.
HAL9001 commented 2026-05-09 05:08:19 +00:00
Owner
Copy link

PR Review Complete — REQUEST_CHANGES

A formal review has been submitted. The core code change (moving namespace filter inside the lock) is correct, but several process/quality requirements are missing before this can be approved:

Blocking Issues

1. Missing concurrency regression test (inline comment on loader.py)

  • Issue #8588 acceptance criteria explicitly require a concurrent list_actors + clear()/discover() test
  • Per CONTRIBUTING.md, all bug fixes require a test that proves the bug existed and passes after the fix
  • No threading/concurrency test for ActorLoader.list_actors exists in any feature file
  • How to fix: Add a Behave scenario to features/actor_loading.feature (or a dedicated features/actor_loader_concurrency.feature) that spawns two threads — one calling list_actors(namespace=...) and one calling clear() simultaneously — asserting no exception and consistent results

2. No TDD companion issue

  • CONTRIBUTING.md requires a Type/Testing TDD issue (TDD: <bug description>) for every bug fix
  • No TDD issue exists for bug #8588
  • The bug fix PR must depend on the TDD issue (TDD issue blocks the fix PR)
  • How to fix: Create a TDD: Race condition in ActorLoader.list_actors — namespace filter applied outside lock issue of Type/Testing + Priority/Critical, then add a Forgejo dependency so this PR depends on (is blocked by) the TDD issue

3. No CHANGELOG entry

  • CONTRIBUTING.md: "Changelog updated with one entry per commit"
  • The single commit in this PR (b5f17123) does not update CHANGELOG.md
  • How to fix: Add an entry under [Unreleased] Fixed in CHANGELOG.md describing the race condition fix, e.g.: - **Thread-safety fix for ActorLoader.list_actors** (#8588): Moved namespace filter inside the lock so the read-and-filter is fully atomic, eliminating a TOCTOU race condition.

4. Commit footer missing ISSUES CLOSED:

  • Every commit must include ISSUES CLOSED: #N in the footer
  • The commit message body ends without this line
  • How to fix: Amend the commit to add ISSUES CLOSED: #8588 as the last line of the footer

5. No CONTRIBUTORS.md update

  • CONTRIBUTING.md: "Add your name if not already listed (first contribution only)" — but also required per the PR checklist for every PR
  • How to fix: Add a CONTRIBUTORS.md entry for this contribution in the same commit

6. PR metadata incomplete

  • No Type/ label applied — should be Type/Bug
  • No milestone assigned — issue #8588 is on milestone v3.2.0; this PR should also be assigned to v3.2.0
  • No Forgejo dependency link set — the PR should block issue #8588 (PR → blocks → issue), not just mention it with "Relates to"

7. Incorrect issue reference in PR body

  • The PR body says Relates to issue #8660 (a weak reference)
  • CONTRIBUTING.md requires Closes #N or Fixes #N with a closing keyword
  • The primary issue is #8588 (the original bug report); #8660 appears to be a duplicate/tracking issue
  • How to fix: Update the PR body to include Closes #8588 (and Closes #8660 if that should also be closed)

What is Correct ✅

  • The one-line structural fix in loader.py is exactly right — the indentation change moves the if namespace is not None: block inside the with self._lock: context manager, ensuring the snapshot used for filtering is always atomic
  • Commit message first line matches the Metadata field in issue #8588 verbatim
  • CI all required gates pass (lint ✅, typecheck ✅, security ✅, unit_tests ✅, coverage ✅, status-check ✅)
  • The benchmark-regression failure is a pre-existing non-required CI job and is not introduced by this PR

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

## PR Review Complete — REQUEST_CHANGES A formal review has been submitted. The core code change (moving namespace filter inside the lock) is **correct**, but several process/quality requirements are missing before this can be approved: ### Blocking Issues **1. Missing concurrency regression test** (inline comment on `loader.py`) - Issue #8588 acceptance criteria explicitly require a concurrent `list_actors` + `clear()`/`discover()` test - Per CONTRIBUTING.md, all bug fixes require a test that proves the bug existed and passes after the fix - No threading/concurrency test for `ActorLoader.list_actors` exists in any feature file - **How to fix**: Add a Behave scenario to `features/actor_loading.feature` (or a dedicated `features/actor_loader_concurrency.feature`) that spawns two threads — one calling `list_actors(namespace=...)` and one calling `clear()` simultaneously — asserting no exception and consistent results **2. No TDD companion issue** - CONTRIBUTING.md requires a `Type/Testing` TDD issue (`TDD: <bug description>`) for every bug fix - No TDD issue exists for bug #8588 - The bug fix PR must depend on the TDD issue (TDD issue blocks the fix PR) - **How to fix**: Create a `TDD: Race condition in ActorLoader.list_actors — namespace filter applied outside lock` issue of `Type/Testing` + `Priority/Critical`, then add a Forgejo dependency so this PR depends on (is blocked by) the TDD issue **3. No CHANGELOG entry** - CONTRIBUTING.md: *"Changelog updated with one entry per commit"* - The single commit in this PR (`b5f17123`) does not update `CHANGELOG.md` - **How to fix**: Add an entry under `[Unreleased] Fixed` in `CHANGELOG.md` describing the race condition fix, e.g.: `- **Thread-safety fix for ActorLoader.list_actors** (#8588): Moved namespace filter inside the lock so the read-and-filter is fully atomic, eliminating a TOCTOU race condition.` **4. Commit footer missing `ISSUES CLOSED:`** - Every commit must include `ISSUES CLOSED: #N` in the footer - The commit message body ends without this line - **How to fix**: Amend the commit to add `ISSUES CLOSED: #8588` as the last line of the footer **5. No `CONTRIBUTORS.md` update** - CONTRIBUTING.md: *"Add your name if not already listed (first contribution only)"* — but also required per the PR checklist for every PR - **How to fix**: Add a `CONTRIBUTORS.md` entry for this contribution in the same commit **6. PR metadata incomplete** - No `Type/` label applied — should be `Type/Bug` - No milestone assigned — issue #8588 is on milestone `v3.2.0`; this PR should also be assigned to `v3.2.0` - No Forgejo dependency link set — the PR should block issue #8588 (`PR → blocks → issue`), not just mention it with "Relates to" **7. Incorrect issue reference in PR body** - The PR body says `Relates to issue #8660` (a weak reference) - CONTRIBUTING.md requires `Closes #N` or `Fixes #N` with a closing keyword - The primary issue is #8588 (the original bug report); #8660 appears to be a duplicate/tracking issue - **How to fix**: Update the PR body to include `Closes #8588` (and `Closes #8660` if that should also be closed) ### What is Correct ✅ - The one-line structural fix in `loader.py` is exactly right — the indentation change moves the `if namespace is not None:` block inside the `with self._lock:` context manager, ensuring the snapshot used for filtering is always atomic - Commit message first line matches the Metadata field in issue #8588 verbatim - CI all required gates pass (lint ✅, typecheck ✅, security ✅, unit_tests ✅, coverage ✅, status-check ✅) - The `benchmark-regression` failure is a pre-existing non-required CI job and is not introduced by this PR --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9000 force-pushed cleveragents-pr-fix-11038 from b5f1712333
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 1m6s
Details
CI / build (pull_request) Successful in 46s
Details
CI / typecheck (pull_request) Successful in 1m47s
Details
CI / benchmark-regression (pull_request) Failing after 1m17s
Details
CI / push-validation (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 2m0s
Details
CI / security (pull_request) Successful in 2m6s
Details
CI / helm (pull_request) Successful in 1m0s
Details
CI / e2e_tests (pull_request) Successful in 4m8s
Details
CI / integration_tests (pull_request) Successful in 4m11s
Details
CI / unit_tests (pull_request) Successful in 6m45s
Details
CI / docker (pull_request) Successful in 2m6s
Details
CI / coverage (pull_request) Successful in 11m58s
Details
CI / status-check (pull_request) Successful in 3s
Details
to 5e9435b175
Some checks failed
CI / build (pull_request) Successful in 1m7s
Details
CI / lint (pull_request) Successful in 1m11s
Details
CI / quality (pull_request) Successful in 1m39s
Details
CI / typecheck (pull_request) Successful in 1m45s
Details
CI / security (pull_request) Successful in 1m45s
Details
CI / helm (pull_request) Successful in 30s
Details
CI / push-validation (pull_request) Successful in 30s
Details
CI / integration_tests (pull_request) Successful in 4m29s
Details
CI / unit_tests (pull_request) Successful in 5m0s
Details
CI / coverage (pull_request) Failing after 3s
Details
CI / docker (pull_request) Failing after 6s
Details
CI / status-check (pull_request) Failing after 3s
Details
2026-05-15 01:37:28 +00:00 Compare
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-05-15 01:46:37 +00:00
Some checks failed
CI / build (pull_request) Successful in 1m7s
Required
Details
CI / lint (pull_request) Successful in 1m11s
Required
Details
CI / quality (pull_request) Successful in 1m39s
Required
Details
CI / typecheck (pull_request) Successful in 1m45s
Required
Details
CI / security (pull_request) Successful in 1m45s
Required
Details
CI / helm (pull_request) Successful in 30s
Details
CI / push-validation (pull_request) Successful in 30s
Details
CI / integration_tests (pull_request) Successful in 4m29s
Required
Details
CI / unit_tests (pull_request) Successful in 5m0s
Required
Details
CI / coverage (pull_request) Failing after 3s
Required
Details
CI / docker (pull_request) Failing after 6s
Required
Details
CI / status-check (pull_request) Failing after 3s
Details
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin cleveragents-pr-fix-11038:cleveragents-pr-fix-11038
git switch cleveragents-pr-fix-11038
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
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!11062
No description provided.