Improve Discord gateway error handling and logging#761
Merged
teknium1 merged 1 commit intoNousResearch:mainfrom Mar 11, 2026
Merged
Conversation
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.
PR improves error handling and logging in the Discord gateway adapter to make operational issues much easier to debug. It replaces bare print statements with structured logging calls and adds detailed logger.error / logger.warning messages (with exc_info=True) around connection failures, timeouts, message send/edit errors, rich media send fallbacks, and channel metadata lookups, while preserving the existing SendResult contract and behavior. With these changes, failures that previously only surfaced as generic error strings or silent fallbacks now emit clear, context-rich log lines that help operators quickly understand what went wrong in Discord integrations