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.

Sign up for GitHub

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

Jump to bottom

[Feat]: Smarter Panic Checks in Logging #53

Open
TylerBloom opened this issue Nov 19, 2022 · 0 comments
Open

[Feat]: Smarter Panic Checks in Logging #53

TylerBloom opened this issue Nov 19, 2022 · 0 comments
Labels
feature Some new is requested good first issue Good for newcomers todo Will be resolved but work hasn't started

Comments

@TylerBloom
Copy link
Member

Description:

Currently, a command has a TTL of 10 seconds before the logging system thinks a panic has occurred. This should be more dynamic as commands that send multiple requests to Discord take much longer.

The solution you'd like:

We should log every await point and/or call to Discord. The logging system should then only detect when more than 10 seconds have passed since the last logged operation.
@TylerBloom TylerBloom added good first issue Good for newcomers feature Some new is requested todo Will be resolved but work hasn't started labels Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Some new is requested good first issue Good for newcomers todo Will be resolved but work hasn't started
Projects
Squire Tournament Services
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TylerBloom