Upgrade to go-msgpack/v2 2.1.1 #292
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds the option to specify what version of the `time.Time` encoding format is desired. The default option is `false`, which preserves compatibility with the current dependency of `hashicorp/go-msgpack 0.5.3` in `go.mod`, but users of this library will probably want to override the the setting. While we're here, test against the latest versions of Go and upgrade the `go.mod` file. I tested that this appears to work with Nomad.
swenson
pushed a commit
to hashicorp/serf
that referenced
this pull request
Oct 19, 2023
This adds the option to specify what version of the `time.Time` encoding format is desired. The default option is `false`, which preserves compatibility with the current dependency of `hashicorp/go-msgpack 0.5.5` in go.mod, but users of this library will probably want to override the the setting. While we're here, upgrade the go.mod file. I tested that this appears to work with Nomad. This needs to be updated and merged after hashicorp/memberlist#292
This was referenced Oct 19, 2023
swenson
pushed a commit
to hashicorp/nomad
that referenced
this pull request
Oct 25, 2023
And set the `time.Time` option to use the go-msgpack-1.1.5-compatible encoding in all the places, since that is the (now previous) version in `go.mod`. v2 2.1.1 was specifically designe to honor backwards compatibility with 1.1.5 and 0.5.5, and to clean up the code base to be more maintainable. There may performance lost with the 1.1.5 to 2.1.1 migration since the fastpath code was removed, but the increased safety is probably worth it. See [the release notes for go-msgkack 2.1.0](https://github.com/hashicorp/go-msgpack/releases/tag/v2.1.0) for more details. I tested this by running this code, and booting up a cluster with a node also running the prior version of Nomad (before the upgrade). Before I made the changes to set the right `time.Time` option, the previous-version node would throw a bunch of time-decoding errors. After fixing the option, the node came up smoothly, even after changing leadership between them. This relies on - [ ] hashicorp/serf#705 - [ ] hashicorp/raft-boltdb#38 - [ ] hashicorp/raft#577 - [ ] hashicorp/memberlist#292 and maybe - [ ] hashicorp/net-rpc-msgpackrpc#12
dhiaayachi
approved these changes
Nov 21, 2023
There was a problem hiding this comment.
Thank you for leading this effort @swenson!
I left few comments but nothing blocking.
.github/workflows/check.yml
Outdated
| @@ -15,7 +15,7 @@ jobs: | |||
| runs-on: ubuntu-latest | |||
| strategy: | |||
| matrix: | |||
| GO_VERSION: [ "1.16","1.17","1.18" ] | |||
| GO_VERSION: [ "1.16","1.17","1.18","1.19","1.20","1.21"" ] | |||
There was a problem hiding this comment.
Shouldn't we only stick with the supported versions of go 🤔 ?
There was a problem hiding this comment.
I only added versions. I didn't want to remove anything. :)
There was a problem hiding this comment.
IMO we should remove the older versions, as to my knowledge none of our supported products is using a non supported version of go and this leave the impression that we still care about those versions.
|
(test failures appear to be unrelated to these changes) |
|
Thanks! |
swenson
pushed a commit
to hashicorp/serf
that referenced
this pull request
Mar 19, 2024
This adds the option to specify what version of the `time.Time` encoding format is desired. The default option is `false`, which preserves compatibility with the current dependency of `hashicorp/go-msgpack 0.5.5` in go.mod, but users of this library will probably want to override the the setting. While we're here, upgrade the go.mod file. I tested that this appears to work with Nomad. This needs to be updated and merged after hashicorp/memberlist#292
swenson
pushed a commit
to hashicorp/serf
that referenced
this pull request
Mar 20, 2024
This adds the option to specify what version of the `time.Time` encoding format is desired. The default option is `false`, which preserves compatibility with the current dependency of `hashicorp/go-msgpack 0.5.5` in go.mod, but users of this library will probably want to override the the setting. While we're here, upgrade the go.mod file. I tested that this appears to work with Nomad. This needs to be updated and merged after hashicorp/memberlist#292
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds the option to specify what version of the
time.Timeencoding format is desired. The default option isfalse, which preserves compatibility with the current dependency ofhashicorp/go-msgpack 0.5.3ingo.mod, but users of this library will probably want to override the the setting.While we're here, test against the latest versions of Go and upgrade the
go.modfile.I tested that this appears to work with Nomad.