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

[Bug]: flaky passthrough-deferred-tools additional_tools stream case under full-suite load

Open
  • Is something wrong?
#7,655 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
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start with tests/responses/passthrough-deferred-tools.test.ts, especially the failing stream case and the assertion at line 242; read how its stub upstream is started and how requests are recorded. Reproduce under full-suite load with the Bun version and command in the issue, then investigate the connection or port race suggested by the missing stub request. Done when the failure is reliably addressed and the full run passes.

Written by the indexing model from the issue text.

Description

bug tools
Client or integration

Other

Area

Tools / MCP / web search

Summary

tests/responses/passthrough-deferred-tools.test.ts > "registered deferred catalog input items authorize calls > responses stream: Write declared via additional_tools" failed once under a full bun run test:changed run (2001 files, 380s, Bun 1.4.3, macOS arm64) and passes 38/38 in isolation on the same tree and on dev ceef4889e4. The proxy logged upstream failure code=upstream_error and the stub upstream recorded zero requests (expect(upstream.seen).toHaveLength(1) received 0, line 242), so the request never reached the local stub; it looks like a load-sensitive connection/port race in the stub upstream rather than a tool-authorization defect.

Reproduction
  1. On dev ceef4889e4 plus the Kimi pricing change (branch feat/kimi-pricing-and-ci-slim-261024, which only touches registry seeds/price rows), run OCX_TEST_RUNNER_BUN=<bun 1.4.3> bun run test:changed on a loaded machine.
  2. Observe the single failure above; rerun the file alone and it passes.
Version

dev ceef4889e4

Operating system

macOS (arm64), Bun 1.4.3 test runner

Provider and model

stub upstream (test fixture)

Logs or error output
[opencodex] upstream failure code=upstream_error
error: expect(received).toHaveLength(expected)
Expected length: 1
Received length: 0
  at tests/responses/passthrough-deferred-tools.test.ts:242:33
(fail) registered deferred catalog input items authorize calls > responses stream: Write declared via additional_tools [76.02ms]
43390 pass / 110 skip / 1 fail
Checks
  • I searched existing issues and documentation.
  • I removed secrets, tokens, account details, request credentials, and personal data.
Dominant language
TypeScript
Stars
16.9k
Forks
1.3k
Avg merge
9h 39m
Merged PRs (30d)
633

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 lidge-jun/opencodex

All issues in lidge-jun/opencodex

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.