space-ai-cutover still expects the sweep's removed 'requests' count (fails on main)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Open tests/app/space-ai-cutover.test.ts and inspect the idempotency assertion around line 190. The issue identifies the mismatch: the sweep now returns four values after the requests count was removed. Update the expected value to [0, 0, 0, []] or compare the documented object keys, then run the focused test with the repository's application check command.

Written by the indexing model from the issue text.

Description

tests/app/space-ai-cutover.test.ts "turned on again before the sweep runs: old work never runs, new work is untouched, the sweep is idempotent" fails:

AssertionError [ERR_ASSERTION]: a second sweep changes nothing
  actual: [ 0, 0, 0, [] ]
  expected: [ 0, 0, 0, 0, [] ]

SpaceAiSwept lost its requests count in #1025 (fdd9e0807, requests between clients go), so the sweep returns four values; line 190 of the test still lists five. Found 2026-11-09 while verifying #1064 (branch claude-hubert/1064-ai-brief rebased on 4e34247b8; the PR does not touch the sweep, its contract or this test): FLUX_TEST_PORT=18880 FLUX_TEST_MAILPIT_PORT=18881 ./scripts/check_application.sh … tests/app/space-ai-cutover.test.ts.

To do: expect [0, 0, 0, []] (or compare the object by its keys).

🤖 Generated with Claude Code

https://claude.ai/code/session_01FocvePm16ECrbtKE1SJ3vc

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
11h 54m
Merged PRs (30d)
371

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 ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.