How to catch ETIMEDOUT error

[moneyDev1111]

Hi, I use ethers 6.3.0, and a script that makes a lot of things and should work for days if not months.. and so it works and all errors are succesfully catched but this one
Error: connect ETIMEDOUT 104.18.35.56:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) { errno: -4039, code: 'ETIMEDOUT', syscall: 'connect', address: '104.18.35.56', port: 443 }
and it stops the script... I wonder why and how should I catch it.. it's seems logically to happen inside of Provider? well ok, still it should be catched? all of the logics is inside the try catch block in my code and any error despite this one doesn't cause the script to stop...
It's like the error is thrown from somewhere outside of the main func which is weird.... Could someone explain how to catch this error? Thank you

[zemse]

and it stops the script

If you are not able to catch the error and the script terminates, I think it's unhandled promise rejection inside ethers.js which might be a bug in ethers.js.

To confirm, can you add this code snippet:

process.on('unhandledRejection', error => {
  console.log('unhandledRejection', error);
});

Expected behaviour after adding this snippet is your script should not stop and the ETIMEDOUT error should keep logging in the console.

[moneyDev1111]

BUT
here's what happened next

and this is when interacting with a deployed contracted estimating fees and calling some other functions that sends tokens... in this case how to be sure what generated the error, still it can be anything right? I mean it can be thrown from any place of code that was run already?

[moneyDev1111]

ALSO

[moneyDev1111]

idk if I should make an issue from this discussion but I think I will just in case

[zemse]

The error in #4066 (reply in thread) seems to be some network-related stuff, I guess it could occur if your internet connection of yours or the destination was disconnected momentarily which caused it.

#4066 (reply in thread) could be a potential ethers.js issue. Can you provide minimal code which can cause that or do you have your source code public?

[moneyDev1111]

` console.log('Sending the tokens...');

const aContract = new ethers.Contract(
	routersAddresses[data[chainFrom].chain.chainId as keyof typeof routersAddresses],
	routerABI,
	signer
);

const estimateSendFee = await aContract.estimateSendFee(
	toBeHex(data[chainTo].chain.chainId),
	acc.address,
	parseUnits(randomAmount, nativeToken.unit),
	false,
	solidityPacked(['uint16', 'uint256'], [1, 700000])
);

const sendTokensTx = await aContract.sendFrom(
	acc.address,
	toBeHex(data[chainTo].chain.chainId),
	acc.address,
	parseUnits(randomAmount, nativeToken.unit),
	acc.address,
	'0x0000000000000000000000000000000000000000',
	solidityPacked(['uint16', 'uint256'], [1, 700000]),
	{
		value: estimateSendFee[0] + parseUnits(randomAmount, nativeToken.unit),
		gasLimit: 500000,
		gasPrice,
	}
);`

this is just estimating the fee and sending tokens, the bug happened maybe once in idk 500 if not 5000 iterations maybe