-
Notifications
You must be signed in to change notification settings - Fork 326
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
Add retries when downloading GraalVM components #6880
Comments
Hubert Plociniczak reports a new STANDUP for yesterday (2023-06-19): Progress: Adding retries to updater. Investigating problems with running benchmarks in SBT for non-runtime project; will need a separate ticket as it doesn't seem to be trivial. Reviewing reported issues, various discussions. It should be finished by 2023-06-20. Next Day: Next day I will be working on the #6880 task. Put up PR with the fix. Pick up next ticket. |
The change adds logic that will attempt a few retries when executing `gu` (GraalVM updater) commands. Previously, if it failed, it failed. Retries should help with the most common case - occassional network hiccups. Note that I don't use an external library for retries on purpose. Didn't want to introduce a yet another dependency for this tiny functionality. Closes #6880.
The change adds logic that will attempt a few retries when executing `gu` (GraalVM updater) commands. Previously, if it failed, it failed. Retries should help with the most common case - occassional network hiccups. Note that I don't use an external library for retries on purpose. Didn't want to introduce a yet another dependency for this tiny functionality. Closes #6880.
The change adds logic that will attempt a few retries when executing `gu` (GraalVM updater) commands. Previously, if it failed, it failed. Retries should help with the most common case - occassional network hiccups. Closes #6880. # Important Notes Note that I don't use an external library for retries on purpose. Didn't want to introduce a yet another dependency for this tiny functionality.
A fresh copy of GraalVM installs all the required components from ttps://www.graalvm.org/component-catalog.
There have been occasions when network can drop or the endpoint return some invalid message, resulting in a broken engine initialization and backend won't start. Successive runs would succeed making the reproduction steps rather cryptic:
The action is currently attempted only once, without any retries. We need a few retries with exponential backoff to deal with random issues that can happen on the way.
The text was updated successfully, but these errors were encountered: