You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the code works so that if a certain microservice fails to be processed, its try-count is increased by 1.
The loop iterates over all unprocessed services until either all are exhausted or all the leftovers have a try-count over 3.
Is this really necessary? Could the analysis first fail and then succeed during the same run?
This arrangement complicates the Native Image logic and data structures.
But still, this logic can be implemented fully inside NativeImageRunner in case the first attempt fails, i.e. the service should be re-tried with the new classpath immediately instead of waiting in the loop for another turn.
Currently, the code works so that if a certain microservice fails to be processed, its try-count is increased by 1.
The loop iterates over all unprocessed services until either all are exhausted or all the leftovers have a try-count over 3.
Is this really necessary? Could the analysis first fail and then succeed during the same run?
This arrangement complicates the Native Image logic and data structures.
I can remove this while working on #9
The text was updated successfully, but these errors were encountered: