-
Notifications
You must be signed in to change notification settings - Fork 266
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
FETCH FAILED: socket error when creating accounts #1783
Comments
Note to whomever picks this up - I've encountered this |
Tried multiple CLI commands & calling from Aztec.js, but can't reproduce this anymore. Are ppl still seeing this?? |
I just updated to the latest sandbox (docker image In particular, I'm consistently seeing it when running the
Also, for a transfer, I get the error when it tries
(Edit: I'm using port 8085, because 8080 is already in use for mainframe access). |
Fixes #1783 Add `failSilently` option to `retry` function. This means that nothing will be printed until we run out of retries, at which point the error will be thrown.
@spypsy why was it failing on the first try, sometimes? What would cause this? |
I spent a lot of time trying to reproduce it reliably and even when I managed to do that, after inserting a bunch of debugging code and trying to figure out why, it stopped failing again. |
In the sandbox guide, we add new stuff to
index.ts
(eg. for retrieving logs, we add the code from the image-1) and runyarn start
. But I also have previous actions in theindex.ts
(eg. creating accounts). After I run yarn start I see the logs as in image-2. We see the error:foundation:retry ERROR TypeError: fetch failed
which suggests that the sandbox failed to create accounts in the first attempt and succeeded in the second one (probably because of some connectivity issue). The reason for this seems unknown but we should ensure that external developers interpret this correctly and don't bother about this error.image-1:
image-2:
The text was updated successfully, but these errors were encountered: