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

Backport of client: avoid unconsumed channel in timer construction into release/1.4.x #15219

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #15215 to be assessed for backporting due to the inclusion of the label backport/1.4.x.

The below text is copied from the body of the original PR.


This PR fixes a bug introduced in #11983 where a Timer initialized with 0
duration causes an immediate tick, even if Reset is called before reading the
channel. The fix is to avoid doing that, instead creating a Timer with a non-zero
initial wait time, and then immediately calling Stop.

Fixes #15198

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-restart-delay/routinely-moving-mullet branch from ce73610 to cc63433 Compare November 11, 2022 15:32
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 8e136a9 into release/1.4.x Nov 11, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/b-restart-delay/routinely-moving-mullet branch November 11, 2022 15:32
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants