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
provider, pubsub, rpc
v0.1.1
macOS (Apple Silicon)
To reproduce: cast code 0xe9ff7ca11280553af56d04ecb8be6b8c4468dcb2 -r /tmp/reth.ipc
cast code 0xe9ff7ca11280553af56d04ecb8be6b8c4468dcb2 -r /tmp/reth.ipc
I don't have a geth on mac, so I cannot test. But I think it should be due to the different OS IPC implementations
Related: #605
The text was updated successfully, but these errors were encountered:
right this check is bad and will terminate the stream if the response exceeds the default buffer capacity:
alloy/crates/transport-ipc/src/lib.rs
Lines 158 to 162 in 5eadbf1
it should be removed, or increased to something more reasonable.
trace responses can exceed ~120MB so we should select a more appropriate limit, since IPC is local we could also remove this entirely.
Sorry, something went wrong.
do you want to take this @publicqi ?
Sure. I'll make a PR.
publicqi
Successfully merging a pull request may close this issue.
Component
provider, pubsub, rpc
What version of Alloy are you on?
v0.1.1
Operating System
macOS (Apple Silicon)
Describe the bug
To reproduce:
cast code 0xe9ff7ca11280553af56d04ecb8be6b8c4468dcb2 -r /tmp/reth.ipc
I don't have a geth on mac, so I cannot test. But I think it should be due to the different OS IPC implementations
Related: #605
The text was updated successfully, but these errors were encountered: