overengineeringstudio / overengineeringstudio/effect-utils

CI proof-surface failures on PR 671 after FOD refresh

Open
#674 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

PR: https://github.com/overengineeringstudio/effect-utils/pull/671
Run: https://github.com/overengineeringstudio/effect-utils/actions/runs/26329049439

After refreshing the stale pnpm-deps fixed-output hashes, the package/lint/typecheck/FOD surfaces are mostly green, but CI remains blocked by proof-surface failures unrelated to the notion-md batch-sync code.

Observed symptoms:

  • Nix/devenv setup intermittently fails fetching public GitHub tarballs with HTTP 401, e.g. nix-community/nixd and pietdevries94/playwright-web-flake.
  • Several rerun jobs were cancelled during setup/proof steps.
  • test-integration-notion also hit a timeout in NotionSearch (integration) > searchStream > streams with filter; this appears outside the notion-md batch-sync path but should be checked for flakiness.

Local proof completed on the PR branch:

  • dt check:quick --no-tui passed.
  • nix build .#genie-pnpm-deps .#megarepo-pnpm-deps .#notion-cli-pnpm-deps .#notion-md-pnpm-deps .#tui-stories-pnpm-deps --print-build-logs passed after hash refresh.

This issue is for CI/proof-surface follow-up, not for secrets or private repo context.

Posted on behalf of @schickling
field value
agent_name 🪵 co2-birch
agent_session_id b324a20a-5b23-4ebb-bb62-29facee69399
agent_tool Codex CLI
agent_tool_version 0.130.0
agent_runtime Codex CLI 0.130.0
agent_model unknown
worktree effect-utils/schickling/2026-05-22-notion-md
machine dev3
tooling_profile dotfiles@unknown-dirty

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

Start with PR 671 and the linked Actions run, then inspect the Nix/devenv setup and proof jobs that fetch the named GitHub tarballs. Check the test-integration-notion searchStream timeout separately; done means the affected CI/proof surfaces complete reliably and the reported integration test behavior is accounted for.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
build-system, ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.