Timeouting on truffle - ethereum

I have been using truffle to deploy my contracts on EVM for quite a while now, and I have been hading many timeout issues saying Error: Too Many Requests.
For me it seems like sometimes it works and sometimes it doesn't, I just keep retrying until it works. Having this with Eth, Bsc and Matic.
Does anyone else have the same issue?

Related

Unable to reproduce Web.dev console errors

Web.dev shows that there are console errors from third party tracking software (LuckyOrange):
WebSocket connection failed: Error in connection establishment:
net::ERR_NAME_NOT_RESOLVED.
Tried to reproduce same error with Lighthouse in Chrome DevTools, also with Lighthouse CLI, Headless Chrome. Was unable to do that. There are no errors in browser console too.
Maybe somebody have experienced the same issue?
I have experience with this. I have always ignored these warnings as they are inconsistent. I THINK they are caused by my CDN blocking the automated requests, resulting in console errors. For me it happens every now and then and only after repeated querying.
Note that I have no proof for this theory.

Ganache hash doesn't match Web3j response with error `TxHashMismatchException`

When trying to run any transaction using Web3j on Ganache it fails with the exception: TxHashMismatchException.
It seems that something has changed on Ganache that is breaking the interoperability.
The issue here is that Ganache has changed the way the transactions hashes are created since version 6.2.0. This problem doesn't exist on version v6.1.8 and earlier, using v6.1.8 should fix your issue.
If you are running Ganache using Docker make sure that you specify the version and not latest.

mist unable to upload smart contract with testrpc

I am struggling to deploy a simple contract on mist.
I am using testrpc which shows all the accounts ans balances properly.
But when I deploy the contract it gives error:
Unable to calculate gas
My mist and geth version are updated to latest.
Please find below the screenshot for error, it keeps on saying unable to estimate gas.
Could find this issue being reported at various places but does not address solution.

Application Error: Application Launch was not detected for application App

When I was validation my Windows Store App I got the following error:
Application Error: Application Launch was not detected for application
App. This could be because your application failed to launch
correctly. Please consider re-running the test and avoid interacting
with the application while tests are running.
What does this mean? The app will not validate.
I thought it was a bit weird and I couldn't find anything when I googled it but people who had almost the same problem as me, though rather than launching it was failing to sleep. This was just plain odd.
I tried to launch the app from Visual Studio 2012 just to prove to myself that it did start properly and for some crazy reason it didn't work. I usually test the game on my Local Machine rather than the Simulator but now, for some reason, it was set to the Simulator and I have been having problems getting it to start lately (the simulator).
I changed it back to the local machine and ran the tests again. This time it worked.
So, if you get this error it might be time to see if your simulator works and if not, have the Local Machine set as default to run with.

Wion32's HttpSendRequest : ERROR_INTERNET_INCORRECT_HANDLE_STAT

I have C++ Win32 app that uses HttpSendRequest to request some URL (via https). It worked OK earlier; but then errors ERROR_INTERNET_INCORRECT_HANDLE_STATE began happen. Why these ones? Any ideas?
I stumbled across something very similar recently. It suggests that your HttpOpenRequest has either failed or not yet completed, or during the HttpSendRequest() call the connection died for some reason (SSL handshake problems, Certificate problems, or just simple TCP connection problems).
I specifically saw the problem when developing an app using the asynchronous WinINET process, and my calls to HttpQueryInfo and InternetReadFile were failing with that return code.
In my case, I wasn't correctly waiting for the async notifications from HttpSendRequest to be received before calling the other methods, and also in cases where I wasn't correctly dealing with failures during the connection.
I know its a year late, but hopefully that helps.
It seems trivial but,
did you have flag INTERNET_FLAG_SECURE in making HttpOpenRequest?
as described in:
http://support.microsoft.com/kb/168151
For I myself was stuck here for hours until I found above knowledge base entry.
I got the same error on Windows XP for HTTPS connection (all flags correct) for the HTTP2 server endpoint, I wonder if it can't properly handle HTTP2 connection or the certificate.