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

Clear timer once it expires, else it is effectively repeating #350

Merged
merged 1 commit into from
Oct 8, 2021

Conversation

jacobmischka
Copy link
Contributor

After the timer "fires" once, we must clear it ourselves, curl does not clear it for us using the callback after calling action, only when it changes. After our curl-provided timeout has expired, fall back to our default timeout, or else we continue polling in a loop.

Closes #348

After the timer "fires" once, we must clear it ourselves, curl does not
clear it for us using the callback after calling `action`, only when it
changes. After our curl-provided timeout has expired, fall back to our
default timeout, or else we continue polling in a loop.
@sagebind
Copy link
Owner

sagebind commented Oct 8, 2021

Thanks for looking into this! Your analysis sounds correct to me. 👍

@sagebind sagebind merged commit 914dfd3 into sagebind:master Oct 8, 2021
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

Successfully merging this pull request may close these issues.

High cpu usage on long requests.
2 participants