Propagate connection errors to outstanding entity sources
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
See https://discuss.lightbend.com/t/handling-upstream-ioexceptions/9285
10.2.x is still compatible with Akka 2.5 which didn't support cancellation cause propagation. Therefore, we cannot report a connection error to a pending response stream on the server.
When we finally drop Akka 2.5.x support in 10.3.0, we should revisit all implementations of `onDownstreamFinish` to propagate cancellation causes accurately.
Contributor guide
Research direction
Start with the linked discussion on upstream IOException handling, then review all implementations of `onDownstreamFinish` in the Akka HTTP codebase. Check how Akka 2.5 limits cancellation-cause propagation and define the 10.3.0 behavior for pending response streams; done means connection errors propagate accurately to outstanding entity sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend-api-design, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100