Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash reports of >4096 characters can cut important information #22

Open
MysticMia opened this issue Jun 5, 2024 · 1 comment
Open

Comments

@MysticMia
Copy link
Collaborator

When the program runs into a crash, it tries to send a message to the guild the crash happened in, or the main server (backup). This often contains a full stack trace of all packages involved. Unfortunately if Rina loses connection to a server (503), it goes through 5 other stack traces as well, ending up with a message of >4096 characters.

A temporary solution was truncating the error messages but better would be to send a second embed or message to send the entire error information.

@MysticMia
Copy link
Collaborator Author

Sending the error in separate messages means there are more logs to clean up if Rina runs into a crashing spree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant