Discrepancy between "current sync status" and "last sync status"
# Summary An ArgoCD Application has a "current sync status" and a "last sync result" which display commit SHAs that can differ. It is not obvious why there would be a difference between these two SHAs (see below). <img width="757" alt="Inconsistency between current sync status and last sync result" src="https://user-images.githubusercontent.com/8124374/140523592-ba864b0d-1fb1-4ce4-a4e0-4e6a79abb7e4.png"> @jannfis explained that "current sync status" shows the “current desired state” (i.e. the latest commit to the target revision) from the last reconciliation operation, while "last sync result" shows the last sync operation where manifests were changed and applied to the cluster. # Motivation The term "sync" seems to be overloaded in the UI labels, which makes it harder to understand whether the live configuration is in sync with the desired configuration. Additionally, after the desired and live manifests are reconciled the "last sync result" is not updated to match the "current sync status" when the reconciliation operation finds that no difference between the live and desired state. # Proposal I would suggest that the text "last sync result" in the UI could be changed to "live state", and the "current sync status" could be changed to "desired state". As a second request, could the "last sync result" SHA be updated to match the "current sync status" SHA after a reconciliation operation that finds no manifests need to be updated? It might also be useful to document
Posted by bilbof on Nov 5, 2021, 2:35 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
New> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Discrepancy between "current sync status" and "last sync status"
# Summary An ArgoCD Application has a "current sync status" and a "last sync result" which display commit SHAs that can differ. It is not obvious why there would be a difference between these two SHAs (see below). <img width="757" alt="Inconsistency between current sync status and last sync result" src="https://user-images.githubusercontent.com/8124374/140523592-ba864b0d-1fb1-4ce4-a4e0-4e6a79abb7e4.png"> @jannfis explained that "current sync status" shows the “current desired state” (i.e. the latest commit to the target revision) from the last reconciliation operation, while "last sync result" shows the last sync operation where manifests were changed and applied to the cluster. # Motivation The term "sync" seems to be overloaded in the UI labels, which makes it harder to understand whether the live configuration is in sync with the desired configuration. Additionally, after the desired and live manifests are reconciled the "last sync result" is not updated to match the "current sync status" when the reconciliation operation finds that no difference between the live and desired state. # Proposal I would suggest that the text "last sync result" in the UI could be changed to "live state", and the "current sync status" could be changed to "desired state". As a second request, could the "last sync result" SHA be updated to match the "current sync status" SHA after a reconciliation operation that finds no manifests need to be updated? It might also be useful to document
Comments (0)
No comments yet. Start the discussion.