-
Notifications
You must be signed in to change notification settings - Fork 238
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
panic: protobuf tag not enough fields in Message.state #1015
Comments
I've not yet looked closely at this, but at a glance I believe it may be a local issue where Nebula is using the |
The fix on Nebula should be dennis-tra/nebula#88. @dennis-tra you can provide an update here after trying the fix. |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
@dennis-tra ping when you are back from OOO :) |
I updated Nebula dependencies last week and decoding protobuf messages from other peers panic:
Downgrading to
github.com/libp2p/go-libp2p-kad-dht
tov0.28.2
and as a consequence alsogithub.com/libp2p/go-libp2p-record
tov0.2.0
(v0.3.0 didn't work) solved the problem. Here's the roll-back commit.I presume it's related to the recent protobuf update: #975
It panics when I do the following:
Does the change require me to decode messages differently?
The text was updated successfully, but these errors were encountered: