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

tests: attribute post-expiry sign-in fetch failure in native auth fixture

Closed
  • Is something wrong?
#2,360 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bun, typescript
Domain
testing

Research direction

Start with packages/ui-react/tests/auth-expiry-runtime.test.ts, especially the bounded until at line 193 and the failing sign-in predicate at lines 418–430; rerun the exact Bun command in the issue’s isolated native-browser setup. Capture the requested request/response or request-failed evidence and origin, route, and interface state, then make a finite comparison that preserves the existing auth, isolation, and cleanup assertions. Done means a supported fixture or product defect is established and tied to a named test, or the execution prerequisite and remaining attribution gap are documented.

Written by the indexing model from the issue text.

Description

area: ci area: ui-react needs: repro priority: p2 type: test

Out of scope

No auth-policy change, weaker account-isolation assertions, timeout increase or claim of credential/data exposure. No production incident or original setup-hook recurrence is established.

Context

During a different #2279 reproduction control at main 2a0b77f675da2f01c32adba3f4920650a5ee09fa, real auth-fixture setup completes before64s. Package build, client bundle, host start and native Chrome launch all complete. The original different-account case (test, packages/ui-react/tests/auth-expiry-runtime.test.ts:418) then fails its post-sign-in predicate at line430 via the existing bounded until at line193.

Actual error: Auth fixture did not settle: f.connected() && f.accountKey() !== null. The captured UI remains on the expired-sign-in surface with Failed to fetch; it says the draft and recordings remain locked until the same account signs in. No later cross-account draft/audio assertions execute, so no isolation bypass or product-auth defect is inferred. Result:0pass/1fail/9filtered/2assertions,84.56s; body20.542s. Cleanup completes at84.561s.

Conditions: isolated frozen install/full build, Bun1.4.3, host Chromium152.0.7977.82, original guarded test and native browser route guards. New diagnostic input RAYON_NUM_THREADS=1 varies the native compiler pool; the installed Tailwind oxide binary contains that option name, but actual thread utilization is unmeasured. Invocation-owned current-UID-preserving user/network namespace, loopback plus a route-free fictional dummy interface, setup capabilities dropped. No source/assertion/deadline change. This is a local execution-context observation, not hosted CI or a causal resource comparison.

Exact-error duplicate search found no existing survivor. #2279 owns setup hook timing, whereas this failure follows completed setup during sign-in; these boundaries remain distinct. Command/log/exit evidence is retained locally.

Scope

Attribute the actual failed sign-in fetch and connection state in this offline native fixture. Distinguish fixture/browser/network prerequisites from application behavior before selecting any correction.

Acceptance criteria

  • Retain exact source and failed predicate, request/response or request-failed evidence, actual origin/route decisions and native online/interface state at the failure.
  • Establish a finite causal comparison preserving real sign-in, expiry, account isolation, drafts/audio and cleanup assertions.
  • If a supported product or fixture defect is established, scope its correction and a named failing/restored test. Otherwise document the execution prerequisite and remaining attribution gap.
  • Preserve existing offline/route guards and deadlines; neither absent runtime evidence nor a later passing run is a repair.

Verification

Original bun run test packages/ui-react/tests/auth-expiry-runtime.test.ts -t 'different account navigates and cannot read or restore prior drafts or audio', inside the isolated route-free namespace above with BRAIN_REQUIRE_CHROME=1 RAYON_NUM_THREADS=1. Full native setup phases remain available. Needs reproduction/attribution; no agent-ready label.

Contract impact

None selected.

2026-10-17: this verification-boundary investigation supports #736. Native parent attachment was attempted and refused with HTTP422: the parent already has the maximum100sub-issues. It remains standalone; no alternate parent or new epic was invented.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
5h 38m
Merged PRs (30d)
960

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 schlessera/brain-kit

All issues in schlessera/brain-kit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.