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 internal/daemon/controller+worker: propagate downstream timeout into release/0.17.x #5100

Conversation

hc-github-team-secure-boundary

Backport

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

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


Propagate the downstream worker timeout into the downstream receiver and downstream ticker so we have a configurable consistent timeout value to use for worker to worker interactions.

Also change the atomic.Pointer to an atomic.Int64 for consistency with other values.


Overview of commits

@hc-github-team-secure-boundary hc-github-team-secure-boundary force-pushed the backport/jbrandhorst-downstream-timeout-propagation/ultimately-choice-horse branch from 7082c8f to 9c64c0e Compare September 11, 2024 16:19
@hc-github-team-secure-boundary hc-github-team-secure-boundary merged commit cf94d91 into release/0.17.x Sep 11, 2024
@hc-github-team-secure-boundary hc-github-team-secure-boundary deleted the backport/jbrandhorst-downstream-timeout-propagation/ultimately-choice-horse branch September 11, 2024 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants