Deployment details page resets selected stage during live polling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened
When viewing the Deployment Details page for a running deployment, manually selecting a stage other than the default active stage is not preserved. While the deployment is running, the page periodically polls for updated deployment data. Each polling cycle resets the selected stage back to the current default active stage, overriding the user's manual selection.
As a result, users cannot continuously inspect logs or details of a non-default stage because their selection is automatically changed every time the deployment data is refreshed.
What you expected to happen
A manually selected stage should remain selected across polling updates. Live polling should update deployment data without overriding the user's current stage selection.
The selected stage should only change automatically when:
- the user opens a different deployment, or
- the user is still following the default active stage and the deployment progresses to a new default stage.
How to reproduce it
- Start or open a deployment that is actively running.
- Navigate to the Deployment Details page.
- Wait until live polling is active.
- Select a stage other than the current default active stage.
- Wait for the next polling interval (approximately every 4 seconds).
- Observe that the selected stage is automatically reset to the default active stage.
Environment
-
piped version:
v0.57.0 -
control-plane version:
v0.57.0 -
Others:
- Operating System: macOS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Deployment Details page's live polling path, focusing on the approximately four-second refresh described in the issue. Reproduce the stage reset with an actively running deployment, then trace how polling updates the deployment data and selected stage. Done means a manually selected non-default stage remains selected across polling, while following the default stage still advances when the deployment progresses.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100