flaky: console e2e specs with route.fetch handlers race disposeFleet (ECONNREFUSED)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
Research direction
Read the listed specs: e2e/console/inbox.spec.ts, shell.spec.ts, views.spec.ts, actions.spec.ts, long-lists.spec.ts, and activity.spec.ts, and compare their teardown with overview.spec.ts and the fix in #867. Check how each spec registers route.fetch() handlers and calls disposeFleet; coordinate the activity.spec.ts change with #853. Done when console e2e tests no longer hit ECONNREFUSED during fleet shutdown.
Written by the indexing model from the issue text.
Description
Follow-up to #866 (fixed in #867 for e2e/console/overview.spec.ts only).
Other console e2e specs stub routes with route.fetch() handlers and shut the fleet down with disposeFleet without first removing them: inbox.spec.ts, shell.spec.ts, views.spec.ts, actions.spec.ts, long-lists.spec.ts, activity.spec.ts. A console request that lands while the gateway closes fails the test with route.fetch: connect ECONNREFUSED, as #866 described.
Likely fix: the same await page.unrouteAll({ behavior: "ignoreErrors" }) before disposeFleet in each, or once in a shared helper. activity.spec.ts is touched by #853's delivery; coordinate with it.
Written by an agent.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 2
- Avg merge
- 8h 8m
- Merged PRs (30d)
- 366
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstackincubator/simlock
-
bug:new
Difficulty 1/5 Under an hour Newbie friendliness 78/100
callstackincubator/simlock#934 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
callstackincubator/simlock#931 ·
Maintainers usually reply within 1 day
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/simlock#817 ·
Maintainers usually reply within 1 day
-
bug:triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
callstackincubator/simlock#778 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 · 1 comment ·
Maintainers usually reply within 1 day
All issues in callstackincubator/simlock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
Maintainers usually reply within 1 day
-
body-parser 2.3.0 in the published ai-dial-chat-bff image is vulnerable (CVE-2026-111181, HIGH)Possibly taken @illya-havsiyevych claimed this today. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
epam/ai-dial-chat#9566 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
はさみアイコンを修正するOpenbug
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
area: core
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day