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

tui3 credit tests read the real OPENROUTER_API_KEY and fail when it is set

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
testing-qa

Research direction

Start in internal/tui3 with TestAFreeCatalogPriceClearsTheWarningWhenTheListArrives and its sibling credit tests. Run the named test with and without OPENROUTER_API_KEY set to reproduce the difference, then inspect how the tests obtain their key or balance source. Done means the affected tests use a controlled source and pass regardless of the process environment.

Written by the indexing model from the issue text.

Description

Since the OpenRouter balance work (#1440), TestAFreeCatalogPriceClearsTheWarningWhenTheListArrives and about nine sibling credit tests in internal/tui3 fail whenever a real OPENROUTER_API_KEY is in the environment, and pass without it.

Repro on santos/dev2 plus #1485's branch:

  • env -u OPENROUTER_API_KEY go test -count=1 -run TestAFreeCatalogPriceClearsTheWarningWhenTheListArrives ./internal/tui3 → ok
  • the same test with a real key exported → FAIL

A test run from a shell or agent that has the key set (common on dev machines and in live-check rigs) goes red for reasons unrelated to the change under test. The tests should pin their own key/balance source instead of reading the process environment.

Dominant language
Go
Stars
115
Forks
14
Avg merge
9h 38m
Merged PRs (30d)
730

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 Agent-Field/CodeAF

All issues in Agent-Field/CodeAF

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.