We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
While downloading a large repository I am receiving the following error:
level=fatal msg="cannot get components: 'Get \"https://<nexus>/service/rest/v1/components?continuationToken=<token>&repository=<repo>\": context deadline exceeded'" func=main.init.func8 file="/home/runner/work/n3dr/n3dr/cmd/n3dr/repositoriesV2.go:113"
What you expected to happen: download the artifacts
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: I have a feeling this might be from a timeout fetching the request
Environment:
n3dr -v
cat /etc/os-release
uname -a
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened:
While downloading a large repository I am receiving the following error:
What you expected to happen:
download the artifacts
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
I have a feeling this might be from a timeout fetching the request
Environment:
n3dr -v
): 7.5.2cat /etc/os-release
):NAME="Amazon Linux"
VERSION="2023"
ID="amzn"
ID_LIKE="fedora"
VERSION_ID="2023"
PLATFORM_ID="platform:al2023"
PRETTY_NAME="Amazon Linux 2023.5.20240701"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
HOME_URL="https://aws.amazon.com/linux/amazon-linux-2023/"
DOCUMENTATION_URL="https://docs.aws.amazon.com/linux/"
SUPPORT_URL="https://aws.amazon.com/premiumsupport/"
BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
VENDOR_NAME="AWS"
VENDOR_URL="https://aws.amazon.com/"
SUPPORT_END="2028-03-15"
uname -a
):The text was updated successfully, but these errors were encountered: