spinframework / spinframework/spin
HTTP Component Timeout
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Hi!
First I'd like to praise the project, pretty cool stuff :)
I'd like to know if there's a way to timeout an HTTP component after a defined amount of time. I have a CPU-bound operation on user data that may even lead to an 'infinite' loop.
Contributor guide
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.
Research direction
The issue names no files, tests, or entry points. Start by investigating how HTTP components execute CPU-bound user operations and whether a configurable timeout exists; done would require a maintainer decision on whether and how this capability should be supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100