Add timeouts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api, backend-api-design
Research direction
The issue names no files, tests, or entry points. First map where parsing, validation, planning, execution, subscriptions, and incremental delivery are handled; done requires an agreed timeout design covering cancellation and the listed operation types.
Written by the indexing model from the issue text.
Description
I've removed timeouts from "operation cost controls" because I feel these are different (but related) concerns. Cost controls typically do counting (depth / list depth / fields per selection set / aliases / resolver calls / @defer instances / input value depth / etc) whereas timeouts are purely temporal and much broader.
Timeouts:
- parsing
- validation
- (planning)
- execution
To be aware of:
- use an abort signal or similar to cancel work when a timeout fires
- share a single abort signal across the entire operation
- subscription operations should have per-event (per-payload) timeouts rather than per-operation
- incremental delivery might want intra-payload timeouts - if the next payload doesn't come in time, cancel everything
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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 graphql/golden-path
-
How to handle authOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
graphql/golden-path#6 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
graphql/golden-path#5 ·
-
Work with OWASPOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
graphql/golden-path#3 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
graphql/golden-path#2 ·
All issues in graphql/golden-path
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Add "append" and "prepend" slots for vue-vuetify extended renderersPossibly taken @simeyc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipsesource/jsonforms#2668 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cobot/zapier#520 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
README の通知条件を実際の判定処理に合わせるPossibly taken @unhappychoice claimed this today. Openfactory:in-progress priority:medium
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unhappychoice/oss-issue-opener#395 · 1 comment ·
Maintainers usually reply within 1 day