Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

test: quiet KV-state ENOENT log spam in TUI consent/dialog tests

Open
  • Is something wrong?
#1,254 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, testing

Research direction

Start by running altimate-base-consent.test.tsx and dialog-altimate-base.test.tsx, then inspect their KV-state setup and the emitted ENOENT stack traces. Confirm whether the tests should use a fixture tmpdir or whether the KV-read miss should be logged once at warn level; done means the tests remain green without repeated stderr noise.

Written by the indexing model from the issue text.

Description

Found during v0.11.0-beta.1 release review (Tech Lead). altimate-base-consent.test.tsx / dialog-altimate-base.test.tsx are functionally green (7-9/9) but emit dozens of Failed to read KV state ... ENOENT .../tmp/opencode/state/kv.json stack traces to stderr per run — a fail-safe path working as designed (no state dir in the test sandbox). Deferred: point the tests at a fixture tmpdir or log the KV-read miss at warn-and-once so the noise doesn't bury a real failure in CI logs.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
1d 19h
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.