Fix arm64 panics by updating google/snappy library to latest, 0.0.4 #11396
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pick up golang/snappy#56 to handle arm64 architectures to fix panics. tldr; Golang 1.16 changed
memmove
implementation for arm64 requiring additional cpu registers that snappy wasn't preserving in its assembly implementation.Other projects have experienced this issue as well, searching for
encode_arm64.s:666
on your favorite search engine will reveal some. Vault updated the dependency earlier this August: hashicorp/vault#12371 .I believe this issue affects Nomad 1.2.x and 1.1.x. Nomad 1.0.x use Golang 1.15 and isn't affected. However, backporting the change to 1.0.x should be harmless.
Fixed #11385 .