Code-Inc/intelligence-terminal
2
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases Wiki Activity

Fix prediction persistence crash after successful LLM ideas #53

New Issue
Closed
opened 2026-07-04 10:25:21 +00:00 by MrSphay · 1 comment
MrSphay commented 2026-07-04 10:25:21 +00:00
Owner
Copy Link

Observed problem

Live validation of the LiteLLM timeout fix generated five valid ideas, then the sweep failed while persisting predictions with Cannot access stableId before initialization.

IntelligenceStore._recordPredictions declares const stableId = stableId(...), shadowing the module helper and triggering the temporal dead zone whenever LLM ideas are present.

Acceptance criteria

  • Rename the local value so the stable ID helper is callable.
  • Add a SQLite-backed regression test that records and reads an LLM prediction.
  • Pass Gitea runner tests and image build.
  • Redeploy and verify a full sweep reports ideasSource=llm without lastSweepError.
## Observed problem Live validation of the LiteLLM timeout fix generated five valid ideas, then the sweep failed while persisting predictions with `Cannot access stableId before initialization`. `IntelligenceStore._recordPredictions` declares `const stableId = stableId(...)`, shadowing the module helper and triggering the temporal dead zone whenever LLM ideas are present. ## Acceptance criteria - Rename the local value so the stable ID helper is callable. - Add a SQLite-backed regression test that records and reads an LLM prediction. - Pass Gitea runner tests and image build. - Redeploy and verify a full sweep reports `ideasSource=llm` without `lastSweepError`.
MrSphay commented 2026-07-04 10:26:29 +00:00
Author
Owner
Copy Link

Fix is in PR #54: #54. The live LLM call already produced five valid ideas; this PR fixes the subsequent persistence failure.

Fix is in PR #54: https://git.wilkensxl.de/Code-Inc/intelligence-terminal/pulls/54. The live LLM call already produced five valid ideas; this PR fixes the subsequent persistence failure.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design-revert
Reverts visual/design changes
 enhancement
New feature or product improvement
 frontend-redesign
Frontend redesign and app-shell/UI work
 marketing-finalization
Product presentation, README, packaging metadata, and customer-facing communication.
 product
User-facing product capability or workflow
 research
Research-originated product idea ready for implementation design
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrSphay Toxic
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Code-Inc/intelligence-terminal#53
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?