fix: add BACKEND_TIMEOUT error code with proper error handling #17
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.
Summary
BACKEND_TIMEOUTerror code constant (-32011) to theerror_codesmoduleBackendTimeoutmatch arm into_error_payload()instead of falling through tointernal_error()BackendTimeouterror code and payload message contentChanges
Previously,
BackendTimeouterrors fell through tointernal_error()into_error_payload(), returning a generic-32603code. Now it returns a specific-32011timeout error code with a descriptive message containing the backend name.This improves client-side error handling by allowing callers to distinguish timeout errors from other internal errors.
Testing
BackendTimeoutintest_error_payload_codetest_backend_timeout_payload_contains_nametest to verify message content