fix(agent/agentcontainers): broadcast devcontainer dirty status over websocket #21100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, when a devcontainer config file was modified, the dirty status was updated internally but not broadcast to websocket listeners. This meant the UI would not show the dirty indicator until some other event triggered a broadcast (e.g., container restart).
Add
broadcastUpdatesLocked()call inmarkDevcontainerDirtyto notify websocket listeners immediately when a config file changes.