-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
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
Pass config object to WebSocketClient #1217
Comments
I need this too, I want to do something like:
Any solution not requiring me to edit and commit the |
Not yet, we ended up overriding the WebSocketClient.js file in /node_modules_override, which is not ideal. |
Is there still no option for this? I cant use the beta with web sockets, every call exceeds max frame size. |
It looks like #1631 added a fix for this which should allow doing web3s = new Web3(new Web3.providers.WebsocketProvider("ws://localhost:8546", {
clientOptions: {
maxReceivedFrameSize: 100000000,
maxReceivedMessageSize: 100000000,
}
})); It is available in |
This is fixed in beta.36 but the setting is web3s = new Web3(new Web3.providers.WebsocketProvider("ws://localhost:8546", {
clientConfig: {
maxReceivedFrameSize: 100000000,
maxReceivedMessageSize: 100000000,
}
})); |
I'm trying to get a payload of 22meg from the blockchain but I get the exception
Frame size of 21980028 bytes exceeds maximum accepted frame size
The
maxReceivedFrameSize
andmaxReceivedMessageSize
are set in the websocket client class. If these are increased the code works fine.Could a config object be passed to
Ws
when its instantiated in web3-providers-ws?The text was updated successfully, but these errors were encountered: