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

500 error mitigation #6

Open
typicalname500 opened this issue Apr 6, 2020 · 3 comments
Open

500 error mitigation #6

typicalname500 opened this issue Apr 6, 2020 · 3 comments
Assignees
@typicalname500
Labels
bug Something isn't working enhancement New feature or request
Milestone
Hey x say y In te...

Comments

@typicalname500
Copy link
Owner

Requests respond intermittently with errors from the API. The idea is to either set up a reliant connection or find another way maybe.
@typicalname500 typicalname500 added the enhancement New feature or request label Apr 6, 2020
@typicalname500 typicalname500 self-assigned this Apr 6, 2020
@typicalname500 typicalname500 added the bug Something isn't working label Apr 7, 2020
@typicalname500
Copy link
Owner Author

Currently, the c# version loops through waiting for 10 seconds before sending the message again. This works with some bad gateway errors but requests that are being actively rejected will be sent forever, further validation needed.

@typicalname500
Copy link
Owner Author

The c# branch now stops making requests after 3 tries and instead sends a message to the user to say that something went wrong.

@typicalname500
Copy link
Owner Author

The python branch now make 3 retries after having a request fails. Will hopefully close when the node js branch is out/ handles response errors too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@typicalname500 typicalname500

Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
Hey x say y In text chat
Development

No branches or pull requests
1 participant
@typicalname500