-
Notifications
You must be signed in to change notification settings - Fork 220
isLastAttempt() is false on the single call to handle error when max-attempts is zero #1395
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
Comments
The problem is that the first reconcile loop has no information from the RetryConfiguration if the builded RetryInfo will actually provide a nextDelay. As it seems that retryConfiguration cannot be null (there is always a default one), Instead of
may be something like
The GenericRetryConfiguration may return false when max-attemps is 0. |
I think it should be rather nullable, thus That is better describing the domain, that there might not be a retry. |
It means that the configuration process is aware of why a given config for a given implementation would not produce a retry so it can set an empty RetryConfiguration instead of the given config/implementation. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
@scrocquesel fixed this here: #1595 pls take a look if you have some time. it is quite simple this way. |
Bug Report
To track the issue raised by quarkiverse/quarkus-operator-sdk#380
The text was updated successfully, but these errors were encountered: