Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Random timeout issues

See original GitHub issue

Checklist

I have looked into the README and have not found a suitable solution or answer.
I have looked into the documentation and have not found a suitable solution or answer.
I have searched the issues and have not found a suitable solution or answer.
I have upgraded to the latest version of this tool and the issue still persists.
I have searched the Auth0 Community forums and have not found a suitable solution or answer.
I agree to the terms within the Auth0 Code of Conduct.

Description

When running the tool with either Export or Import I am randomly getting Timeout errors. I am running the export command which worked a couple of times and then it did not work a few times now it is working again.

a0deploy export --config_file Sandbox.json --format yaml --output_folder ./Sandbox

This error appears at random stages.

APIError: connect ETIMEDOUT ***.**.***.**:443

I switched internet connect, from WLAN to LAN to mobile LTE. Same behavior.

The following is happening when I run it from GitHub Actions:

Expectation

The command to work!

Reproduction

Run the command in the description

Deploy CLI version

7.15.1

Node version

v16.13.0

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

ewanharriscommented, Oct 27, 2022

@Franklin89, Node.js 19 could possibly alleviate some of the pressure from the amount of requests as it enables keepAlive by default. That should allow HTTPS connections to be reused by multiple requests rather than opening a new connection every time.

For folks that hit this type of issue it might be worthwhile testing out Node.js 19 to see if it is more stable

0reactions

willveddcommented, Nov 28, 2022

Closing this one out. While the Deploy CLI can certainly be resource-hungry at times, it does so for performance reasons. Perhaps there is room for optimization in the future, but until then, there is clear guidance on how to “fix”.