overengineeringstudio / overengineeringstudio/effect-utils

Harden the 'wake id rotates' assertion in scheduled-compose.integration.test.ts to quiescence

Open Beginner friendly
#768 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:effect origin:agent type:chore
Dominant language
TypeScript
Stars
82
Forks
2
Avg merge
1d 8h
Merged PRs (30d)
121

Description

Problem

scheduled-compose.integration.test.ts has a polling-race flake in the wake id rotates assertion: it samples the rotating wake id while the poll loop is still advancing, so under parallel CPU load the observed id can be a cycle ahead/behind the expectation. Same class of issue as the earlier recurrence-count flake fix.

Fix

  • Harden the assertion to wait for quiescence (the loop reaching a stable, settled state) before sampling the wake id, rather than reading it mid-flight — mirroring the recurrence-flake hardening.

Refs #757.

Posted on behalf of @schickling
field value
agent_name 🥇 cl2-pyrite
agent_session_id a71a7fca-0ccf-427e-9e57-51aea841dc74
agent_tool Claude Code
agent_tool_version 2.1.165
agent_runtime Claude Code 2.1.165
agent_model claude-opus-4-8
runtime_profile /nix/store/sz4ll7nq7qbwcsw65pw13w5hw61lnvk5-coding-agent-runtime-profile/share/coding-agents/profile.json
skills_manifest /nix/store/nhbhipdhwmcqh669bpr15g39hr17cqbb-agent-skills-corpus/share/agent-skills/manifest.json
worktree effect-utils/schickling/2026-06-08-restate-effect
machine dev3
tooling_profile dotfiles@7360c0d

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Open scheduled-compose.integration.test.ts and locate the “wake id rotates” assertion. Read the recurrence-count flake fix referenced in #757, then run the relevant scheduled-compose integration test to observe the polling behavior. Done means the assertion samples the wake id only after the loop reaches quiescence and the test remains reliable under parallel CPU load.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.