envoyproxy/envoy

wasm: protect against blocking scripts

Open

#14,126 opened on Nov 20, 2020

View on GitHub
 (6 comments) (3 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

An infinite loop in a Wasm script causes envoy worker to spin and block. Envoy does not respond to ^C. A well-meaning module might have long loops that are potentially taking too much of work. Ideally, the module should be able to yield back strategically and let Envoy handle book keeping business (e.g. potentially stopping the script if the request is interrupted).

Contributor guide

Research direction
Investigate how Wasm modules can yield control back to the Envoy host to prevent infinite loops. Look into existing mechanisms like 'wasmtime' async support or callback based yielding.
Tech stack
wasm
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++WebAssembly basicsEnvoy proxy context
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60