Switch to a different murmurhash2 implementation to handle unicode characters #9158
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.
References
Port of jupyterlab/debugger#549
Code changes
This change vendors the implementation of the murmurhash implementation we were using: https://github.com/garycourt/murmurhash-js
This implementation was for ascii strings only: https://github.com/garycourt/murmurhash-js/blob/0197ce38bedac0e05f40b9d7152095d06db8292c/murmurhash2_gc.js#L9
See jupyterlab/debugger#549 for more context.
The vendored implementation is heavily based on the js implementation, but uses a
TextEncoder
to encode the string into aUint8Array
before running the algorithm, so it behaves the same as the original C++ implementation (used on xeus-python).User-facing changes
Before
After
Backwards-incompatible changes
None