You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running go1.23.6 run enc.go | go1.22.7 run dec.go surfaces some kind of compatibility issue.
What did you see happen?
code/go/gob » go1.23.6 run enc.go | go1.22.7 run dec.go
2025/02/26 16:07:31 Failed to gob decode empty x.509 cert: gob: wrong type ([]x509.OID) for received field Certificate.Policies
The "real world" issue is that this seems to be causing all of our pre-compiled plugins to fail when running on a go1.23 build of Mattermost server (we just bumped Golang version from 1.22.7 to 1.23.6).
What did you expect to see?
No backward compatibility decoding error.
2025/02/26 16:07:43 Decoded empty x.509 cert
The text was updated successfully, but these errors were encountered:
seankhliao
changed the title
gob: wrong type ([]x509.OID) for received field Certificate.Policies
encoding/gob: wrong type ([]x509.OID) for received field Certificate.Policies
Feb 26, 2025
@seankhliao Thanks for the quick response. I am noting that this issue could result in significant impact and disruption on our side (essentially what happened last time, see #66249 (comment)). As far as I understand it's effectively a breaking change that would require us to re-compile and re-release all of our supported plugins to avoid breakage.
Would you know if there's any recommended workaround other than recompiling?
Go version
go1.23.6 amd64 and go1.22.7 amd64
Output of
go env
in your module/workspace:What did you do?
Given the following sample programs:
enc.go
dec.go
Running
go1.23.6 run enc.go | go1.22.7 run dec.go
surfaces some kind of compatibility issue.What did you see happen?
The "real world" issue is that this seems to be causing all of our pre-compiled plugins to fail when running on a go1.23 build of Mattermost server (we just bumped Golang version from 1.22.7 to 1.23.6).
What did you expect to see?
No backward compatibility decoding error.
The text was updated successfully, but these errors were encountered: