Repository navigation
Say why a lagging request is disconnected - #1003
Merged
Merged
Conversation
Requests that fall too far behind the last final block got the server shutdown error. Give each of the two cases its own error.
🔍 Vulnerabilities of
|
| digest | sha256:7ba30e1e0c4e2ae4c0c5d02345db8ebb69ee0a956515a58955e9da15460100b0 |
| vulnerabilities |     |
| platform | linux/amd64 |
| size | 127 MB |
| packages | 382 |
📦 Base Image ubuntu:24.04
| also known as |
|
| digest | sha256:f610ab94648195aa356059f5b41d6085c9d4d903c072430cdd1af7bdb646106b |
| vulnerabilities |    |
sduchesneau
marked this pull request as ready for review
October 16, 2026 15:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A production request that falls more than 2 segments behind the last final block is disconnected so the client reconnects and back-processes the gap in parallel. Both places that do this returned the server shutdown error,
endpoint is shutting down, please reconnect. Each now has its own error, stillUnavailable:pipeline.ErrBackprocessEndedTooFarBehindwhen back-processing finishes too far behind (service/tier1.go)pipeline.ErrStreamFellTooFarBehindwhen streamed final blocks fall behind (checkFinalBlockLag)service/error.gomaps both toUnavailablefor connect and gRPC clients, and a new test checks the code and message on both paths.