This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 797
feat: implement IPC transport support #260
Merged
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
35a9473
Initial IPC setup
austinabell e2f2b1d
Cleanup
austinabell ab99ffe
Oops
austinabell bf27127
change futures dependency reference
austinabell 679fd3b
Document, add prints, cleanup
austinabell aed6b5f
Fix logic
austinabell 13026b8
Make result type consistent with crate
austinabell 388ede6
Setup geth ipc config and tests
austinabell 21decf3
Cleanup subscription test
austinabell f10de9e
Switch hash function to siphash
austinabell 3c8bf93
Update dep usage for ordering
austinabell e1a4795
Use tempfile for better cleanup (and OS support)
austinabell faf4b0b
Replace prints with tracing logs
austinabell e5ba57d
Ignore test with Celo feat
austinabell 40b0389
Merge branch 'master' of github.com:gakonst/ethers-rs into ipc
austinabell 073ff36
chore: remove debug logs and use default geth ipc path
gakonst File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you really need higher performance than
SipHasher
(I would suggest measuring), and don't care about hashDoS (theahash
crate is not designed to be hashDoS resistant, despite what the author might claim), I would suggest using thetwox-hash
crate which implements the XXHash algorithm.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'm aware of this, but figured this usage wouldn't require that property, but maybe I'm overlooking some concern. Thanks for the link, I'll look into that, but I'll just change to whatever @gakonst prefers since I don't have an opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've switched it to siphash as a default, but happy to switch to whatever is preferred :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. I think using what the standard library provides is a reasonable starting point, and if you need better performance, it would be good to measure whether a 3rd-party hashing crate actually provides an improvement.