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

Stacktraces in logs #1165

Closed
rr- opened this issue Feb 23, 2024 · 0 comments · Fixed by #1166
Closed

Stacktraces in logs #1165

rr- opened this issue Feb 23, 2024 · 0 comments · Fixed by #1166
Labels
Feature New functionality
Milestone

Comments

@rr-
Copy link
Collaborator

rr- commented Feb 23, 2024

Every now and then people come in on Discord asking about crashes, especially with custom levels. Typically it's natural to refer to the the logs for crash details in these situations. However, our current builds don't provide that information and cut off the logs instead, rendering them meaningless for debugging purposes. It would be helpful to implement meaningful stacktrace reporting in the logs when crashes happen.

@rr- rr- added the Feature New functionality label Feb 23, 2024
@rr- rr- added this to the 3.2 milestone Feb 23, 2024
rr- added a commit that referenced this issue Feb 24, 2024
@rr- rr- mentioned this issue Feb 24, 2024
2 tasks
rr- added a commit that referenced this issue Feb 24, 2024
rr- added a commit that referenced this issue Feb 24, 2024
rr- added a commit that referenced this issue Feb 24, 2024
rr- added a commit that referenced this issue Feb 24, 2024
@rr- rr- closed this as completed in #1166 Feb 24, 2024
rr- added a commit that referenced this issue Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant