-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[dashboard, (server?)] Inconsistent derivation of prebuild status #8197
Comments
/cc @jldec I tried to dig up all places in the code I could think off. Might still be incomplete. |
A concrete bug caused by this: #8592 |
Out of the instances listed, only the following remain:
|
Closing, completed except for 1 instance. The only remaining instance is |
This leads to inconsistencies in our UI (prebuild says "FAILED", but re-triggering yields "cannot start - still running") and strange errors (hanging on prebuild logs).
Examples where we're interested in the state/properties of a prebuild, but use different sources:
I don't think that all of those usages are wrong per-se, but I think the fact that we see such a variety of ways to answer the same question is a strong hint that our data model/API lags functionality or reliability.
IMO it's worth going through all cases and understand the motivation and problems that the current API poses and fix those.
The text was updated successfully, but these errors were encountered: