This repository has been archived by the owner on Jun 27, 2023. It is now read-only.
fix: _emitMessages should not emit normalized messages #79
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The latest release for message signing resulting in normalized messages being emitted internally. This broke the existing api as the
fromproperty is a buffer instead of a string.This adds tests to ensure that a publish call results in normalized
_forwardMessagescalls, but non normalized_emitMessagescalls.This was uncovered in the js-ipfs cli pubsub test suite and fixes it, https://travis-ci.com/ipfs/js-ipfs/jobs/198483511#L1069