perf(test): replace per-instance _database_initialized flag with process-global cache #1264

Merged

freemo merged 1 commit from perf/m3-global-db-initialized-cache into master 2026-04-02 16:58:40 +00:00

Conversation 4 Commits 1 Files changed 3 +168

brent.edwards commented 2026-04-02 06:02:52 +00:00

Member

Copy link

Summary

Adds a process-global _INITIALIZED_DBS: set[str] cache to features/environment.py that short-circuits repeated _fast_init_or_upgrade calls for the same database URL. This eliminates ~65,000 unnecessary function-body executions per full test run (URL parsing, path extraction, prefix matching, and stat() syscalls) — approximately 7 UnitOfWork instantiations × 10,700 scenarios.

Changes

features/environment.py

• Added _INITIALIZED_DBS: set[str] = set() module-level set with documentation referencing issue #735.
• Modified _fast_init_or_upgrade closure:
  • Added if db_url in _INITIALIZED_DBS: return early check at the top (before any URL parsing).
  • Added _INITIALIZED_DBS.add(db_url) after both successful paths (non-empty file detection and template copy).
• Added _INITIALIZED_DBS.clear() in before_scenario to prevent cross-scenario state leaks.

features/fast_init_upgrade.feature

• Added 4 new @mock_only scenarios for the global cache:
  • Second call for non-empty DB is a cache hit
  • Second call for newly-copied template DB is a cache hit
  • Cache clearing between scenarios works correctly
  • Non-matching prefix URLs are not cached

features/steps/fast_init_upgrade_steps.py

• Added _get_initialized_dbs() helper that accesses the cache through _fast_init_or_upgrade.__globals__ to correctly resolve Behave's exec_file() namespace isolation.
• Added step definitions for all new cache-related scenarios.

Design Decisions

1. Simple set over thread-local: Behave runs scenarios sequentially within a worker process; thread safety is not a concern.
2. Cache only fast-path URLs: Non-SQLite, in-memory, and non-matching-prefix URLs delegate to _original_init_or_upgrade and are not cached.
3. Clear in before_scenario: Each scenario gets fresh temp-DB paths, so prior entries are stale and would waste memory.
4. __globals__ access in tests: Behave loads environment.py via exec_file() into a private hooks dict, creating a separate namespace from features.environment.__dict__. Test steps read the cache through the closure function's __globals__ to access the same set object.

Quality Gates

Gate	Result
nox -s lint	✅ Pass
nox -s typecheck	✅ Pass
nox -s unit_tests (parallel)	✅ Pass (13,787 scenarios)
nox -s unit_tests (serial)	✅ Pass (13,787 scenarios)
nox -s integration_tests	✅ Pass
nox -s coverage_report	✅ 98.7% (threshold: 97%)
nox -s benchmark	✅ Pass
nox -s security_scan	✅ Pass
nox -s dead_code	✅ Pass
nox -s docs	✅ Pass
nox -s build	✅ Pass

Closes #735

## Summary Adds a process-global `_INITIALIZED_DBS: set[str]` cache to `features/environment.py` that short-circuits repeated `_fast_init_or_upgrade` calls for the same database URL. This eliminates ~65,000 unnecessary function-body executions per full test run (URL parsing, path extraction, prefix matching, and `stat()` syscalls) — approximately 7 `UnitOfWork` instantiations × 10,700 scenarios. ## Changes ### `features/environment.py` - Added `_INITIALIZED_DBS: set[str] = set()` module-level set with documentation referencing issue #735. - Modified `_fast_init_or_upgrade` closure: - Added `if db_url in _INITIALIZED_DBS: return` early check at the top (before any URL parsing). - Added `_INITIALIZED_DBS.add(db_url)` after both successful paths (non-empty file detection and template copy). - Added `_INITIALIZED_DBS.clear()` in `before_scenario` to prevent cross-scenario state leaks. ### `features/fast_init_upgrade.feature` - Added 4 new `@mock_only` scenarios for the global cache: - Second call for non-empty DB is a cache hit - Second call for newly-copied template DB is a cache hit - Cache clearing between scenarios works correctly - Non-matching prefix URLs are not cached ### `features/steps/fast_init_upgrade_steps.py` - Added `_get_initialized_dbs()` helper that accesses the cache through `_fast_init_or_upgrade.__globals__` to correctly resolve Behave's `exec_file()` namespace isolation. - Added step definitions for all new cache-related scenarios. ## Design Decisions 1. **Simple `set` over thread-local**: Behave runs scenarios sequentially within a worker process; thread safety is not a concern. 2. **Cache only fast-path URLs**: Non-SQLite, in-memory, and non-matching-prefix URLs delegate to `_original_init_or_upgrade` and are not cached. 3. **Clear in `before_scenario`**: Each scenario gets fresh temp-DB paths, so prior entries are stale and would waste memory. 4. **`__globals__` access in tests**: Behave loads `environment.py` via `exec_file()` into a private hooks dict, creating a separate namespace from `features.environment.__dict__`. Test steps read the cache through the closure function's `__globals__` to access the same set object. ## Quality Gates | Gate | Result | |---|---| | `nox -s lint` | ✅ Pass | | `nox -s typecheck` | ✅ Pass | | `nox -s unit_tests` (parallel) | ✅ Pass (13,787 scenarios) | | `nox -s unit_tests` (serial) | ✅ Pass (13,787 scenarios) | | `nox -s integration_tests` | ✅ Pass | | `nox -s coverage_report` | ✅ 98.7% (threshold: 97%) | | `nox -s benchmark` | ✅ Pass | | `nox -s security_scan` | ✅ Pass | | `nox -s dead_code` | ✅ Pass | | `nox -s docs` | ✅ Pass | | `nox -s build` | ✅ Pass | Closes #735

brent.edwards added 1 commit 2026-04-02 06:02:52 +00:00

perf(test): replace per-instance _database_initialized flag with process-global cache ... 2bf1c627eb

Add a process-global `_INITIALIZED_DBS: set[str]` to `features/environment.py`
that caches database URLs after `_fast_init_or_upgrade` has processed them.
On subsequent calls with the same URL, the function returns immediately —
skipping all URL parsing, path extraction, prefix matching, and `stat()`
syscalls that previously executed on every new `UnitOfWork` instance.

The cache is cleared at the start of each scenario in `before_scenario` to
prevent cross-scenario state leaks, since each scenario receives fresh
temp-DB paths via `tempfile.mktemp()`.

Key implementation detail: test step definitions access `_INITIALIZED_DBS`
through `_fast_init_or_upgrade.__globals__` rather than importing from
`features.environment`, because Behave loads environment.py via `exec_file()`
into a private hooks dict — a separate namespace from the Python module.

Four new Behave scenarios validate cache hits on repeated calls, cache
clearing between scenarios, and non-caching of non-matching-prefix URLs.

Estimated savings: ~65,000 unnecessary function-body executions eliminated
per full test run (~7 UnitOfWork instantiations × ~10,700 scenarios).

ISSUES CLOSED: #735

brent.edwards added this to the v3.2.0 milestone 2026-04-02 06:02:57 +00:00

brent.edwards added the

Type

Task

label 2026-04-02 06:02:58 +00:00

freemo self-assigned this 2026-04-02 06:15:10 +00:00

freemo commented 2026-04-02 08:03:08 +00:00

Owner

Copy link

🔒 Claimed by pr-reviewer-1. Starting independent code review.

🔒 Claimed by pr-reviewer-1. Starting independent code review.

freemo approved these changes 2026-04-02 08:05:44 +00:00

Dismissed

freemo left a comment

Copy link

Code Review — APPROVED ✅

Summary

Clean, well-implemented performance optimization that adds a process-global _INITIALIZED_DBS: set[str] cache to features/environment.py, eliminating ~65,000 unnecessary _fast_init_or_upgrade function-body executions per full test run.

Review Findings

Specification Alignment ✅

• This is a test infrastructure optimization that doesn't touch production code. No spec alignment concerns.

Correctness ✅

• Cache check is placed at the very top of _fast_init_or_upgrade, before any URL parsing — maximizes performance benefit.
• Both successful paths (non-empty file detection and template copy) correctly add to the cache.
• Non-SQLite, in-memory, and non-matching-prefix URLs correctly delegate to the original and are never cached.
• Empty-string URLs fall through to the original (via the startswith("sqlite") check) and are never cached.
• Cache is cleared in before_scenario — correct, since each scenario gets fresh temp-DB paths.

Thread Safety ✅

• A plain set is appropriate: Behave runs scenarios sequentially within a worker process. In parallel mode (behave-parallel), each worker is a separate process with its own _INITIALIZED_DBS set.

Test Quality ✅

• 4 new @mock_only Behave scenarios cover: cache hit for non-empty DB, cache hit after template copy, cache clearing between scenarios, and non-caching of non-matching-prefix URLs.
• The _get_initialized_dbs() helper correctly uses __globals__ to access the cache through the closure's namespace (necessary due to Behave's exec_file() loading), with a clear docstring explaining why.

Code Quality ✅

• Well-documented with block comments referencing issue #735.
• Follows existing patterns in the file.
• No unnecessary complexity.

Commit Message ✅

• Conventional Changelog format with detailed body and ISSUES CLOSED: #735 footer.
• Single atomic commit with clean history.

Security ✅

• No secrets, no injection risks. Change is purely in test infrastructure.

No issues found. Approving for merge.

## Code Review — APPROVED ✅ ### Summary Clean, well-implemented performance optimization that adds a process-global `_INITIALIZED_DBS: set[str]` cache to `features/environment.py`, eliminating ~65,000 unnecessary `_fast_init_or_upgrade` function-body executions per full test run. ### Review Findings **Specification Alignment** ✅ - This is a test infrastructure optimization that doesn't touch production code. No spec alignment concerns. **Correctness** ✅ - Cache check is placed at the very top of `_fast_init_or_upgrade`, before any URL parsing — maximizes performance benefit. - Both successful paths (non-empty file detection and template copy) correctly add to the cache. - Non-SQLite, in-memory, and non-matching-prefix URLs correctly delegate to the original and are never cached. - Empty-string URLs fall through to the original (via the `startswith("sqlite")` check) and are never cached. - Cache is cleared in `before_scenario` — correct, since each scenario gets fresh temp-DB paths. **Thread Safety** ✅ - A plain `set` is appropriate: Behave runs scenarios sequentially within a worker process. In parallel mode (behave-parallel), each worker is a separate process with its own `_INITIALIZED_DBS` set. **Test Quality** ✅ - 4 new `@mock_only` Behave scenarios cover: cache hit for non-empty DB, cache hit after template copy, cache clearing between scenarios, and non-caching of non-matching-prefix URLs. - The `_get_initialized_dbs()` helper correctly uses `__globals__` to access the cache through the closure's namespace (necessary due to Behave's `exec_file()` loading), with a clear docstring explaining why. **Code Quality** ✅ - Well-documented with block comments referencing issue #735. - Follows existing patterns in the file. - No unnecessary complexity. **Commit Message** ✅ - Conventional Changelog format with detailed body and `ISSUES CLOSED: #735` footer. - Single atomic commit with clean history. **Security** ✅ - No secrets, no injection risks. Change is purely in test infrastructure. No issues found. Approving for merge.

freemo referenced this pull request 2026-04-02 08:05:54 +00:00

perf(test): replace per-instance _database_initialized flag with process-global cache #735

freemo commented 2026-04-02 16:54:59 +00:00

Owner

Copy link

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

freemo approved these changes 2026-04-02 16:58:28 +00:00

freemo left a comment

Copy link

Independent Code Review — APPROVED ✅

Reviewer: reviewer-pool-1 (second independent review)

Summary

Clean, well-scoped performance optimization that adds a process-global _INITIALIZED_DBS: set[str] cache to features/environment.py, eliminating ~65,000 redundant _fast_init_or_upgrade function-body executions per full test run. No production code is touched — this is purely test infrastructure.

Review Findings

Specification Alignment ✅

• Test infrastructure optimization only. No production code or spec-governed interfaces are affected.

Correctness ✅

• Cache check is placed at the very top of _fast_init_or_upgrade, before any URL parsing — maximizes the performance benefit.
• Both successful paths (non-empty file detection at L501 and template copy at L507) correctly add to the cache.
• Non-SQLite, in-memory, bare sqlite://, and non-matching-prefix URLs correctly delegate to the original and are never cached — these are the right exclusions.
• Empty-string URLs fall through to the original via the startswith("sqlite") check and are never cached.
• Cache is cleared in before_scenario — correct placement since each scenario gets fresh temp-DB paths. If TDD tag validation fails and before_scenario returns early before the clear, the next scenario's before_scenario will clear it, so no cross-scenario leak is possible.

Thread Safety ✅

• A plain set is appropriate: Behave runs scenarios sequentially within a worker process. In parallel mode (behave-parallel), each worker is a separate process with its own _INITIALIZED_DBS set — no shared state.

Test Quality ✅

• 4 new @mock_only Behave scenarios cover all important cache behaviors:
  1. Cache hit for non-empty DB (second call short-circuits)
  2. Cache hit after template copy (second call short-circuits)
  3. Cache clearing between scenarios works correctly
  4. Non-matching-prefix URLs are not added to the cache
• The _get_initialized_dbs() helper correctly uses __globals__ to access the cache through the closure's namespace (necessary due to Behave's exec_file() loading), with a clear docstring explaining the rationale.
• Step definitions have proper type annotations and descriptive docstrings.

Type Safety ✅

• _INITIALIZED_DBS: set[str] = set() — properly annotated module-level variable.
• All new functions have complete type annotations on parameters and return types.
• No # type: ignore suppressions added (the existing one on L510 is pre-existing for the monkey-patch assignment).

Commit Message ✅

• Conventional Changelog format: perf(test): replace per-instance _database_initialized flag with process-global cache
• Detailed body explaining the change, rationale, and implementation details.
• Proper ISSUES CLOSED: #735 footer.
• Single atomic commit — clean history.

PR Metadata ✅

• Type/Task label present.
• Milestone v3.2.0 assigned.
• Closes #735 in PR body.
• Detailed description with design decisions documented.

Security ✅

• No secrets, no injection risks. Change is purely in test infrastructure.

Code Quality ✅

• Well-documented with block comments referencing issue #735.
• Follows existing patterns in the file.
• No unnecessary complexity — simple set-based caching with clear lifecycle management.

No issues found. Approving for merge.

## Independent Code Review — APPROVED ✅ **Reviewer:** reviewer-pool-1 (second independent review) ### Summary Clean, well-scoped performance optimization that adds a process-global `_INITIALIZED_DBS: set[str]` cache to `features/environment.py`, eliminating ~65,000 redundant `_fast_init_or_upgrade` function-body executions per full test run. No production code is touched — this is purely test infrastructure. ### Review Findings **Specification Alignment** ✅ - Test infrastructure optimization only. No production code or spec-governed interfaces are affected. **Correctness** ✅ - Cache check is placed at the very top of `_fast_init_or_upgrade`, before any URL parsing — maximizes the performance benefit. - Both successful paths (non-empty file detection at L501 and template copy at L507) correctly add to the cache. - Non-SQLite, in-memory, bare `sqlite://`, and non-matching-prefix URLs correctly delegate to the original and are never cached — these are the right exclusions. - Empty-string URLs fall through to the original via the `startswith("sqlite")` check and are never cached. - Cache is cleared in `before_scenario` — correct placement since each scenario gets fresh temp-DB paths. If TDD tag validation fails and `before_scenario` returns early before the clear, the *next* scenario's `before_scenario` will clear it, so no cross-scenario leak is possible. **Thread Safety** ✅ - A plain `set` is appropriate: Behave runs scenarios sequentially within a worker process. In parallel mode (behave-parallel), each worker is a separate process with its own `_INITIALIZED_DBS` set — no shared state. **Test Quality** ✅ - 4 new `@mock_only` Behave scenarios cover all important cache behaviors: 1. Cache hit for non-empty DB (second call short-circuits) 2. Cache hit after template copy (second call short-circuits) 3. Cache clearing between scenarios works correctly 4. Non-matching-prefix URLs are not added to the cache - The `_get_initialized_dbs()` helper correctly uses `__globals__` to access the cache through the closure's namespace (necessary due to Behave's `exec_file()` loading), with a clear docstring explaining the rationale. - Step definitions have proper type annotations and descriptive docstrings. **Type Safety** ✅ - `_INITIALIZED_DBS: set[str] = set()` — properly annotated module-level variable. - All new functions have complete type annotations on parameters and return types. - No `# type: ignore` suppressions added (the existing one on L510 is pre-existing for the monkey-patch assignment). **Commit Message** ✅ - Conventional Changelog format: `perf(test): replace per-instance _database_initialized flag with process-global cache` - Detailed body explaining the change, rationale, and implementation details. - Proper `ISSUES CLOSED: #735` footer. - Single atomic commit — clean history. **PR Metadata** ✅ - `Type/Task` label present. - Milestone v3.2.0 assigned. - `Closes #735` in PR body. - Detailed description with design decisions documented. **Security** ✅ - No secrets, no injection risks. Change is purely in test infrastructure. **Code Quality** ✅ - Well-documented with block comments referencing issue #735. - Follows existing patterns in the file. - No unnecessary complexity — simple set-based caching with clear lifecycle management. No issues found. Approving for merge.

freemo merged commit 5437c73420 into master 2026-04-02 16:58:40 +00:00

freemo deleted branch perf/m3-global-db-initialized-cache 2026-04-02 16:58:44 +00:00

freemo referenced this pull request from a commit 2026-04-02 16:58:44 +00:00

perf(test): replace per-instance _database_initialized flag with process-global cache (#1264)

freemo referenced this pull request 2026-04-02 16:58:50 +00:00

perf(test): replace per-instance _database_initialized flag with process-global cache #735

freemo referenced this pull request 2026-04-02 17:11:30 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request 2026-04-02 17:20:01 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request 2026-04-02 17:34:51 +00:00

[Automated] Product Build Session State #1393

freemo referenced this pull request 2026-04-02 18:20:08 +00:00

[UAT-SUPERVISOR] v3.7.0 TUI — Pool Supervisor LAUNCHED (16 workers) #1447

Sign in to join this conversation.

Reviewers

No reviewers

freemo

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

freemo

2 participants

Notifications

Subscribe

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!1264

No description provided.