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

Bump default timeout to 2m #509

Merged
merged 1 commit into from
Aug 16, 2019
Merged

Bump default timeout to 2m #509

merged 1 commit into from
Aug 16, 2019

Conversation

brian-brazil
Copy link
Contributor

The current default of 10s is problematic when testing slower probes
from a browser. Cancellation will still work as a fallback,
including for older Prometheus servers that don't send the timeout
header, so there shouldn't be a big buildup of ongoing probes.

Fixes #259

Signed-off-by: Brian Brazil brian.brazil@robustperception.io

The current default of 10s is problematic when testing slower probes
from a browser. Cancellation will still work as a fallback,
including for older Prometheus servers that don't send the timeout
header, so there shouldn't be a big buildup of ongoing probes.

Fixes #259

Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>
@juliusv
Copy link
Member

juliusv commented Aug 16, 2019

👍

@brian-brazil brian-brazil merged commit 4bf1892 into master Aug 16, 2019
@brian-brazil brian-brazil deleted the timeout branch August 16, 2019 12:43
brian-brazil pushed a commit that referenced this pull request Jul 29, 2020
Since #509 (4bf1892) the default
timeout was changed to 2m. This change updates the README to reflect it.

Signed-off-by: Pedro Araujo <phcrva@gmail.com>
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.

Confusing timeout behaviour
2 participants