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 deps: update go-memdb for goroutine leak fix into release/1.3.x #14985

Merged

Conversation

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

Backport

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

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

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


May as well slip this in for the bugfix releases
hashicorp/go-memdb#128

@hashicorp-cla
Copy link

hashicorp-cla commented Oct 20, 2022

CLA assistant check
All committers have signed the CLA.

manual cherry-pick

* deps: update go-memdb for goroutine leak fix

* cl: update for goroutine leak go-memdb
@shoenig shoenig force-pushed the backport/deps-update-go-memdb/willingly-absolute-alien branch from 9053c37 to 30c5dd0 Compare October 20, 2022 15:40
@shoenig shoenig merged commit 7996f64 into release/1.3.x Oct 20, 2022
@shoenig shoenig deleted the backport/deps-update-go-memdb/willingly-absolute-alien branch October 20, 2022 16:39
@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 Feb 19, 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.

None yet

3 participants