I know nothing about blockchain, but these might apply.
@sudosammy this looks to be related to your logs query, which is scanning the entire blockchain and thus taking too long to complete so the websocket connection appears idle and you are disconnected.
Try using a smaller query on only the most recent, say, ~1000 blocks. The data from older blocks will never change so should be cached in your Dapp, not queried from the chain each time the Dapp is loaded.
The reason this works on ropsten is that its a much smaller chain with less events, so the query can be performed in time.
const RINKEBY_WSS = "wss://rinkeby.infura.io/ws";
var provider = new Web3.providers.WebsocketProvider(RINKEBY_WSS);
var web3 = new Web3(provider);
provider.on('error', e => console.log('WS Error', e));
provider.on('end', e => {
console.log('WS closed');
console.log('Attempting to reconnect...');
provider = new Web3.providers.WebsocketProvider(RINKEBY_WSS);
provider.on('connect', function () {
console.log('WSS Reconnected');
});
web3.setProvider(provider);
});
As far as try/catch - that only works for synchronous code.
If you really wanted to dig into the error you can always put debug stuff inside the web3.js code in the node_modules folder. But I strongly doubt you’d need to get to that level for something as basic as this.
What happens when you try the end event? Does it get to that point?
Obviously if this can be cause by a shitty network, then it’s a basic situation that any package should be able to handle. But it wouldn’t be unlike a third-party node service to expect you to roll your own restart. That code with the restart inside the error event handler looks like how a lot of node services handle crashes. It seems likely it has to be something like that.
Excuse me sir, but that is the string concatenation operator.
The real problem is I tried to string-concatenate things that weren’t strings, so JS had to coerce them to strings so that the operation of string-concatenation would be well-defined.
Ah I see the issue, you mistakenly think that plus is the string concatenation operator, it’s not, if you want to concatenate strings you should use the template string feature. HTH!
I think it’s extra-funny that the string concatenation operator is not even the idiomatic way to concatenate strings.
Actually, I looked at the spec, and the interesting thing is that the domain of + as mathematical addition is narrower than the other operators. So ”3” - 1 === 2, but ”3” + 1 === “31”. This also means that +/- aren’t associative. And if you have
const x = y - z;
return a + x;
It’s actually technically unsound to refactor by inlining x to give return a + y - z.
The female programmer who isn’t allowed to speak is ready to work at Google.
It’s funny this was still in the days when they thought programming was like the typing pool and should be relegated to women. Then right when programming got cool the dudes all shoved the women out of the way.
