Replace ErrorType::{NotReady, ShuttingDown} by new ServerError variant - #1138
Merged
Conversation
|
||||||||||||||||||
|
Test Coverage: 80.10% |
svix-pluiz
approved these changes
Apr 27, 2026
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
2 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.
On the SDK side, there are only going to be three "types" of errors as currently planned (see https://github.com/svix/diom-docs/pull/6), but I think server-side it makes sense to distinguish "expected" server errors (
not_ready,shutting_down, alsorequest_timeoutonce #1118 is merged) which we don't need toerror!-log for and unexpectedinternalerrors for which we want toerror!, and also have origin information (thetracestuff).Part of #1128.