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

fix(provider): remove FakeListLLM defaults #427

Closed
freemo wants to merge 1 commit from feature/m4-provider-fixes into master
pull from: feature/m4-provider-fixes
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 25 +1273 -144
freemo commented 2026-02-25 03:29:32 +00:00
Owner
Copy link

Summary

Closes #323. Removes hard-coded FakeListLLM defaults from provider configuration to prevent test fixtures from leaking into production code paths. Replaces the silent None return when no providers are configured with a fail-fast ProviderNotConfiguredError, adds an explicit mock_providers settings flag with a guard that blocks accidental mock usage outside test mode, implements provider auto-detection with trace logging (chosen provider and selection reason), and introduces a resolve_provider_by_name() helper that emits clear errors when a requested provider is unknown or missing credentials.

Changes

  • Provider Registry (src/cleveragents/providers/registry.py): Added resolve_provider_by_name() for explicit provider lookup with descriptive errors. Added DEBUG-level trace logging to get_default_provider_type() so every selection path (env override, settings default, auto-detected, none found) emits the chosen provider and the reason.
  • Container (src/cleveragents/application/container.py): Replaced the silent return None fallback when no providers are configured with ProviderNotConfiguredError. Added debug logging for mock-mode activation and final provider selection.
  • Settings (src/cleveragents/config/settings.py): Added mock_providers boolean field (env: CLEVERAGENTS_MOCK_PROVIDERS) with a startup validation guard that warns when the flag is set but CLEVERAGENTS_TESTING_USE_MOCK_AI is not enabled.
  • Exceptions (src/cleveragents/core/exceptions.py): Added ProviderNotConfiguredError subclass of ProviderError for missing-provider scenarios.
  • Agent graphs (auto_debug.py, context_analysis.py, plan_generation.py): Updated provider wiring to use the validated registry path instead of direct FakeListLLM fallbacks.
  • Tests (Behave): Added features/provider_fixes.feature with 104 lines of BDD scenarios and features/steps/provider_fixes_steps.py (447 lines) covering provider auto-detection, mock flag validation, fail-fast behavior, and trace logging.
  • Tests (Robot): Added robot/provider_detection.robot and robot/helper_provider_detection.py for integration-level provider detection smoke tests.
  • Tests (ASV): Added benchmarks/provider_selection_bench.py for provider resolution baseline benchmarks.
  • CHANGELOG: Added entry describing the FakeListLLM defaults removal.

Dependencies

  • Blocks issue #323 (this PR must be merged before the issue can be closed)
## Summary Closes #323. Removes hard-coded FakeListLLM defaults from provider configuration to prevent test fixtures from leaking into production code paths. Replaces the silent `None` return when no providers are configured with a fail-fast `ProviderNotConfiguredError`, adds an explicit `mock_providers` settings flag with a guard that blocks accidental mock usage outside test mode, implements provider auto-detection with trace logging (chosen provider and selection reason), and introduces a `resolve_provider_by_name()` helper that emits clear errors when a requested provider is unknown or missing credentials. ### Changes - **Provider Registry** (`src/cleveragents/providers/registry.py`): Added `resolve_provider_by_name()` for explicit provider lookup with descriptive errors. Added `DEBUG`-level trace logging to `get_default_provider_type()` so every selection path (env override, settings default, auto-detected, none found) emits the chosen provider and the reason. - **Container** (`src/cleveragents/application/container.py`): Replaced the silent `return None` fallback when no providers are configured with `ProviderNotConfiguredError`. Added debug logging for mock-mode activation and final provider selection. - **Settings** (`src/cleveragents/config/settings.py`): Added `mock_providers` boolean field (env: `CLEVERAGENTS_MOCK_PROVIDERS`) with a startup validation guard that warns when the flag is set but `CLEVERAGENTS_TESTING_USE_MOCK_AI` is not enabled. - **Exceptions** (`src/cleveragents/core/exceptions.py`): Added `ProviderNotConfiguredError` subclass of `ProviderError` for missing-provider scenarios. - **Agent graphs** (`auto_debug.py`, `context_analysis.py`, `plan_generation.py`): Updated provider wiring to use the validated registry path instead of direct FakeListLLM fallbacks. - **Tests (Behave)**: Added `features/provider_fixes.feature` with 104 lines of BDD scenarios and `features/steps/provider_fixes_steps.py` (447 lines) covering provider auto-detection, mock flag validation, fail-fast behavior, and trace logging. - **Tests (Robot)**: Added `robot/provider_detection.robot` and `robot/helper_provider_detection.py` for integration-level provider detection smoke tests. - **Tests (ASV)**: Added `benchmarks/provider_selection_bench.py` for provider resolution baseline benchmarks. - **CHANGELOG**: Added entry describing the FakeListLLM defaults removal. ## Dependencies - Blocks issue #323 (this PR must be merged before the issue can be closed)
freemo added this to the v3.0.0 milestone 2026-02-25 03:30:00 +00:00
freemo commented 2026-02-26 03:06:32 +00:00
Author
Owner
Copy link

CONTRIBUTING.md Compliance Review

Passing

  • Closing keyword in description: Closes #323 is present.
  • Forgejo dependency link: PR #427 correctly blocks issue #323; issue #323 correctly depends on PR #427. Direction is correct per CONTRIBUTING.md § Linking and Dependencies.
  • Type label: Type/Bug is present (exactly one Type/ label).
  • Milestone: v3.0.0 is assigned and matches issue #323's milestone.
  • Conventional Changelog format: Both commit subject lines (fix(provider): ... and docs: ...) follow the standard.
  • PR description: Updated to include a detailed summary of changes, motivation, and file-level breakdown.

Issues Requiring Fixes

  1. Commit message bodies are empty (CONTRIBUTING.md § Commit Message Format, § First Line vs. Commit Body):
    Both commits have only a subject line with no body. The issue's Definition of Done explicitly requires: "A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation." The main commit (fc115f73) changes 21 files with 1,150 insertions — this warrants a substantive body explaining what was done and why.

  2. Commit messages missing issue reference footer (CONTRIBUTING.md § Pull Request Process, requirement 4):
    "Every commit in the PR must reference the issue it addresses in its commit message footer (e.g., ISSUES CLOSED: #45 or Refs: #45)." Neither commit includes ISSUES CLOSED: #323 or Refs: #323 in the footer.

  3. CHANGELOG update in a separate commit (CONTRIBUTING.md § Commit Completeness):
    "Update ancillary files. Configuration, build scripts, changelogs, and other metadata affected by the change should be updated in the same commit." The CHANGELOG entry is in a separate docs: commit (a33ce4e6) rather than included in the main fix(provider): commit (fc115f73). These two commits should be squashed into one so the changelog update accompanies the code change.

Recommended Fix

Squash the two commits into a single commit with:

  • First line: fix(provider): remove FakeListLLM defaults (matching issue #323 Metadata exactly)
  • Body: A description of the implementation (provider auto-detection, mock_providers flag, ProviderNotConfiguredError, trace logging, test additions)
  • Footer: ISSUES CLOSED: #323
## CONTRIBUTING.md Compliance Review ### Passing - **Closing keyword in description**: `Closes #323` is present. - **Forgejo dependency link**: PR #427 correctly **blocks** issue #323; issue #323 correctly **depends on** PR #427. Direction is correct per CONTRIBUTING.md § Linking and Dependencies. - **Type label**: `Type/Bug` is present (exactly one `Type/` label). - **Milestone**: `v3.0.0` is assigned and matches issue #323's milestone. - **Conventional Changelog format**: Both commit subject lines (`fix(provider): ...` and `docs: ...`) follow the standard. - **PR description**: Updated to include a detailed summary of changes, motivation, and file-level breakdown. ### Issues Requiring Fixes 1. **Commit message bodies are empty** (CONTRIBUTING.md § Commit Message Format, § First Line vs. Commit Body): Both commits have only a subject line with no body. The issue's Definition of Done explicitly requires: *"A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation."* The main commit (`fc115f73`) changes 21 files with 1,150 insertions — this warrants a substantive body explaining what was done and why. 2. **Commit messages missing issue reference footer** (CONTRIBUTING.md § Pull Request Process, requirement 4): *"Every commit in the PR must reference the issue it addresses in its commit message footer (e.g., `ISSUES CLOSED: #45` or `Refs: #45`)."* Neither commit includes `ISSUES CLOSED: #323` or `Refs: #323` in the footer. 3. **CHANGELOG update in a separate commit** (CONTRIBUTING.md § Commit Completeness): *"Update ancillary files. Configuration, build scripts, changelogs, and other metadata affected by the change should be updated in the same commit."* The CHANGELOG entry is in a separate `docs:` commit (`a33ce4e6`) rather than included in the main `fix(provider):` commit (`fc115f73`). These two commits should be squashed into one so the changelog update accompanies the code change. ### Recommended Fix Squash the two commits into a single commit with: - **First line**: `fix(provider): remove FakeListLLM defaults` (matching issue #323 Metadata exactly) - **Body**: A description of the implementation (provider auto-detection, mock_providers flag, ProviderNotConfiguredError, trace logging, test additions) - **Footer**: `ISSUES CLOSED: #323`
freemo force-pushed feature/m4-provider-fixes from a33ce4e6cf
Some checks failed
CI / lint (pull_request) Successful in 21s
Details
CI / quality (pull_request) Successful in 29s
Details
CI / security (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 52s
Details
CI / integration_tests (pull_request) Failing after 4m23s
Details
CI / unit_tests (pull_request) Failing after 16m31s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 21m36s
Details
CI / coverage (pull_request) Failing after 54m6s
Details
to a709e11092
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 21s
Details
CI / quality (pull_request) Successful in 40s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / security (pull_request) Successful in 54s
Details
CI / integration_tests (pull_request) Failing after 3m23s
Details
CI / unit_tests (pull_request) Failing after 9m44s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 20m47s
Details
CI / coverage (pull_request) Failing after 34m24s
Details
2026-02-26 10:14:45 +00:00 Compare
freemo scheduled this pull request to auto merge when all checks succeed 2026-02-26 10:15:07 +00:00
freemo force-pushed feature/m4-provider-fixes from a709e11092
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 21s
Details
CI / quality (pull_request) Successful in 40s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / security (pull_request) Successful in 54s
Details
CI / integration_tests (pull_request) Failing after 3m23s
Details
CI / unit_tests (pull_request) Failing after 9m44s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 20m47s
Details
CI / coverage (pull_request) Failing after 34m24s
Details
to 333576a823
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / integration_tests (pull_request) Failing after 3m52s
Details
CI / unit_tests (pull_request) Failing after 10m30s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 21m15s
Details
CI / coverage (pull_request) Failing after 33m59s
Details
2026-02-26 11:49:25 +00:00 Compare
freemo force-pushed feature/m4-provider-fixes from 333576a823
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / integration_tests (pull_request) Failing after 3m52s
Details
CI / unit_tests (pull_request) Failing after 10m30s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 21m15s
Details
CI / coverage (pull_request) Failing after 33m59s
Details
to 5baa4f2e28
Some checks failed
CI / lint (pull_request) Successful in 16s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 28s
Details
CI / security (pull_request) Successful in 34s
Details
CI / build (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 1m2s
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-02-26 15:24:16 +00:00 Compare
freemo force-pushed feature/m4-provider-fixes from 5baa4f2e28
Some checks failed
CI / lint (pull_request) Successful in 16s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 28s
Details
CI / security (pull_request) Successful in 34s
Details
CI / build (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 1m2s
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 88eb4de677
Some checks failed
CI / lint (pull_request) Successful in 25s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 17s
Details
CI / build (pull_request) Successful in 23s
Details
CI / security (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 1m11s
Details
CI / integration_tests (pull_request) Failing after 4m46s
Details
CI / unit_tests (pull_request) Failing after 21m22s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 24m4s
Details
CI / coverage (pull_request) Failing after 45m8s
Details
2026-02-26 15:25:51 +00:00 Compare
freemo force-pushed feature/m4-provider-fixes from 88eb4de677
Some checks failed
CI / lint (pull_request) Successful in 25s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 17s
Details
CI / build (pull_request) Successful in 23s
Details
CI / security (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 1m11s
Details
CI / integration_tests (pull_request) Failing after 4m46s
Details
CI / unit_tests (pull_request) Failing after 21m22s
Details
CI / docker (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 24m4s
Details
CI / coverage (pull_request) Failing after 45m8s
Details
to 5e2d6b8b5d
Some checks failed
CI / lint (pull_request) Successful in 14s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 32s
Details
CI / security (pull_request) Successful in 34s
Details
CI / build (pull_request) Successful in 31s
Details
CI / integration_tests (pull_request) Failing after 5m21s
Details
CI / benchmark-regression (pull_request) Successful in 20m4s
Details
CI / unit_tests (pull_request) Failing after 28m1s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Failing after 1h22m44s
Details
2026-02-26 16:53:15 +00:00 Compare
freemo force-pushed feature/m4-provider-fixes from 5e2d6b8b5d
Some checks failed
CI / lint (pull_request) Successful in 14s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 32s
Details
CI / security (pull_request) Successful in 34s
Details
CI / build (pull_request) Successful in 31s
Details
CI / integration_tests (pull_request) Failing after 5m21s
Details
CI / benchmark-regression (pull_request) Successful in 20m4s
Details
CI / unit_tests (pull_request) Failing after 28m1s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Failing after 1h22m44s
Details
to cdd4244ae1
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Failing after 13s
Details
CI / build (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 23s
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / typecheck (pull_request) Has been cancelled
Details
CI / security (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
2026-02-26 18:47:55 +00:00 Compare
freemo force-pushed feature/m4-provider-fixes from cdd4244ae1
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Failing after 13s
Details
CI / build (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 23s
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / typecheck (pull_request) Has been cancelled
Details
CI / security (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
to 5c122a31e9
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 20s
Details
CI / lint (pull_request) Failing after 22s
Details
CI / security (pull_request) Successful in 33s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Has been skipped
Details
CI / integration_tests (pull_request) Failing after 2m32s
Details
CI / unit_tests (pull_request) Failing after 9m58s
Details
CI / docker (pull_request) Has been skipped
Details
2026-02-26 18:48:20 +00:00 Compare
freemo scheduled this pull request to auto merge when all checks succeed 2026-02-26 18:49:57 +00:00
freemo commented 2026-02-26 19:04:19 +00:00
Author
Owner
Copy link

Im going to close this and start over here...

Im going to close this and start over here...
freemo closed this pull request 2026-02-26 19:04:19 +00:00
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Required
Details
CI / quality (pull_request) Successful in 20s
Required
Details
CI / lint (pull_request) Failing after 22s
Required
Details
CI / security (pull_request) Successful in 33s
Required
Details
CI / typecheck (pull_request) Successful in 54s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / benchmark-regression (pull_request) Has been skipped
Details
CI / integration_tests (pull_request) Failing after 2m32s
Required
Details
CI / unit_tests (pull_request) Failing after 9m58s
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
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.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#323 fix(provider): remove FakeListLLM defaults
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!427
No description provided.