feat(session): introduce proper error handling - #100
Merged
Conversation
…f handle_client/websocket endpoint this commit introduces better backend error handling based on messages whenever an error occurs, it is returned and routed by the view layer, and only the offending socket receives the warning closes #31
Co-authored-by: Codex <codex@openai.com>
|
Contributor
Author
|
Os testes foram mais pra aumentar o code coverage mesmo, nn me preocuparia tanto com eles a menos que a gnt mude funcionalidade depois e algum teste quebre. daí recomendo ver o q está sendo testado |
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.
Agora o backend retorna mensagens/envelopes de erro quando um evento dá um erro no dispatch da engine.
No caso de erros internos, também retorna o request_id. mas se o json estava mal-formatado, não retorna o request_id
closes #31