Regression with updating container state

[begunfx]

Drydock version

1.5.0-rc.7

What happened?

When I trigger a manual update of a container it shows queued while updating but that's it. Then after it just disappears from the list of containers with updates. We're missing the "Updating" state.

What did you expect?

See above

Steps to reproduce

See above

Relevant configuration

Logs

Installation method

Docker Compose

Docker version

24.0.1

OS / Architecture

Synology DSM 7

[begunfx]

Sorry, this is probably technically a duplicate of: #256 That's what happens when you post right before bed. ;-)

[begunfx]

Adding to this. It looks like this regressive behavior is only for single container updates. When I do an "Update All" I see the current container as "Updating 1 of 2" and the other container as something like "Queued 2 of 2", which is great and expected behavior. The issue is when updating just one container we are getting the wrong state: "Queued" instead of the expected "Updating". Hope that clarifies things. Thanks!

[begunfx]

Another update: I updated another container and did see the "Updating" state but only for a second then it when to "Queued". Either way single container updates should probably not have a "Queued" state at all.

[s-b-e-n-s-o-n]

This has been addressed in the upcoming RC.

• Root cause: The queue-aware update state introduced in rc.7 inadvertently broke the standalone (non-queued) update state transitions. When a container went from Queued straight to completion, the "Updating" state was never shown.
• Fix: Restored the standalone update state handling path so containers properly transition through Queued → Updating → Updated (2b00c4b8)

This also relates to the fixes in #291 (dashboard update-start semantics) and #276 (notification tracking). The next RC will be out shortly — please verify you see the full state progression when triggering individual container updates.