[ryanking13]

fix #287

WSGI streaming response use stack switching. However, they should use the same contextvars, since they are in the same request context.

[ask-bonk]

LGTM

github run

[clanky-the-clanker]

This pull request's reviews are posted as pull request reviews: see the review of 0f1d4e8d.

[clanky-the-clanker]

✅ Approved — No issues found: the fix runs the app call, iteration and close in one shared request context, and new tests cover sharing within a stream, isolation between streams and reset on cancel.

_{The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.}

---

✅ All checks passed

🔒 Security: ✅ LGTM

No security concerns.

---

📖 AGENTS.md: ✅ LGTM

No AGENTS.md updates needed.

---

📋 Code Quality: ✅ LGTM

No issues found.

• wsgi.py: one copied contextvars.Context covers the app call, iter(result), every next() and close(). App-set values stay visible during streaming, and tokens reset in the context that created them.
• Cleanup: the try/finally in close_all closes wsgi.input even if closing the iterable raises.
• Tests: the workerd WSGI tests cover sharing within a stream, isolation between concurrent streams, and token reset on cancel. The Flask tests exercise stream_with_context.

---

⚡ Performance: ✅ LGTM

No performance concerns. Running each chunk through context.run adds very little overhead.

---

📝 Documentation: ✅ LGTM

No documentation issues.

---

_{Reviewed commit: 0f1d4e8d}