No timeout on any outbound request
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- backend, networking
Research direction
Start with the three fetch locations: src/auth/meetup-token-provider.ts:66, src/meetup/graphql-client.ts:46, and src/meetup/image-service.ts:78. Read the existing network error handling and the write-path retry wording before updating the calls. Done means stalled requests time out after 30 seconds, timeouts map to the network category, and write operations retain the existing inspection-before-retry guidance.
Written by the indexing model from the issue text.
Description
Summary
All three outbound HTTP calls use bare fetch with no AbortSignal. A stalled connection hangs the tool call indefinitely, and a stdio MCP server has no other liveness mechanism, so the client is left waiting with no error and no way to tell the difference between slow and dead.
Locations
src/auth/meetup-token-provider.ts:66(token exchange)src/meetup/graphql-client.ts:46(all reads and writes)src/meetup/image-service.ts:78(image upload)
Suggested fix
Add signal: AbortSignal.timeout(30_000) to each call, and map the resulting TimeoutError onto the existing network error category. The write paths already have good "this may have succeeded, inspect Meetup before retrying" wording that should apply to a timeout too.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. 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 SSWConsulting/SSW.MeetupMCP
-
Area: Backend Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Type: DevOps
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Area: Backend Type: Refactor
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Type: Bug Type: DevOps
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Area: Backend Type: Bug
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in SSWConsulting/SSW.MeetupMCP
Similar issues
-
ADD openalgoOpentemplate
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
vercel/ai#21528 · 3 comments ·
Maintainers usually reply within 1 day
-
bug Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/fluentui-contrib#671 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sveltejs/acorn-typescript#150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100