Skip to content
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

Request timeout error for version of Gradle that I never used #46

Closed
eygraber opened this issue Aug 11, 2021 · 7 comments
Closed

Request timeout error for version of Gradle that I never used #46

eygraber opened this issue Aug 11, 2021 · 7 comments
Milestone

Comments

@eygraber
Copy link

I randomly get the following error using v1:

Error: Request timeout: /distributions/gradle-6.8-rc-4-wrapper.jar.sha256

I currently use 7.1.1 and never used 6.80-rc-4

@JLLeitschuh
Copy link
Contributor

How regularly do you see this issue?

@eygraber
Copy link
Author

eygraber commented Sep 1, 2021

I haven't seen it since filing the issue, and I only saw it a few times overall.

@petertrr
Copy link

I started facing similar issues today. My repo uses gradle version 7.2 and wrapper-validation-action@v1, and in logs I have seen
Error: Request timeout: /distributions/gradle-7.0-rc-2-wrapper.jar.sha256
Error: Request timeout: /distributions/gradle-6.5-wrapper.jar.sha256

@dweiss
Copy link

dweiss commented Oct 27, 2021

The same in Lucene:
image
Lucene is on an entirely different gradle version than the one shown here.

@maho7791
Copy link

I get this error as well. We use Gradle 7.1.1

Run gradle/wrapper-validation-action@v1
  with:
    min-wrapper-count: 1
    allow-snapshots: false
  env:
    LC_ALL: en_US.UTF-8
Error: connect ETIMEDOUT 104.18.165.99:443

It happend randomly. Because we run a Matrix of Java 11 and 16 with ubuntu_latest and windows_latest, we get this error almost every time.

@JLLeitschuh
Copy link
Contributor

@eskatos are we keeping the existing connection open when we retry? Should we try to make sure we're opening a new connection when we retry? Thoughts?

@bigdaz
Copy link
Member

bigdaz commented Feb 1, 2024

This should be fixed by #167

@bigdaz bigdaz closed this as completed Feb 1, 2024
@bigdaz bigdaz added this to the v2.1.0 milestone Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants