We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be convenient if the protocol ID that is not supported by the remote peer is returned as well in the error message.
Current:
protocol not supported
Desired:
protocol not supported: <protocol_ID>
The text was updated successfully, but these errors were encountered:
Not opposed to it, but is this particularly useful? You know which protocol(s) you were trying to negotiate when you receive this error.
If we wanted to add the protocol IDs, we'd run into #1886 again.
This is a go-multistream issue, not a go-libp2p issue by the way. Moving it there.
Sorry, something went wrong.
moved to multiformats/go-multistream#94 closing this
No branches or pull requests
It would be convenient if the protocol ID that is not supported by the remote peer is returned as well in the error message.
Current:
protocol not supported
Desired:
protocol not supported: <protocol_ID>
The text was updated successfully, but these errors were encountered: