Deployment details page resets selected stage during live polling
维护者通常 2 天内回复
评估
调研方向
从 Deployment Details 页面实时轮询的路径开始，重点关注 issue 中描述的约四秒刷新。使用一个正在运行的 deployment 重现 stage 重置，然后跟踪轮询如何更新 deployment 数据和所选 stage。完成的标准是：手动选择的非默认 stage 在轮询期间保持选中，而跟随默认 stage 时，仍会随着 deployment 的进展而继续前进。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Go
- 星标
- 1.4k
- 派生
- 391
- 平均合并
- 4 天 1 小时
- 30 天内合并 PR
- 58
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pipe-cd/pipecd 的其他 Issue
-
Applications at the repository root are not triggered by new commits可能已有人在做 @Daksha1611 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 2 天内回复
-
pipedv1 kubernetes plugins ignore trafficRouting.istio.host in K8S_TRAFFIC_ROUTING可能已有人在做 @Dhirenderchoudhary 今天认领。 未关闭
难度 2/5 半天 新手友好度 74/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 2 天内回复
-
pipectl transfer restore application drops backed-up labels可能已有人在做 @bhavishyajain545 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 2 天内回复
相似的 Issue
-
needs-triage typo
难度 1/5 1 小时以内 新手友好度 88/100
llm-d-incubation/llm-d-scaling-manager#122 ·
维护者通常 1 天内回复
-
good first issue severity: low tech-debt
难度 2/5 半天 新手友好度 75/100
TMHSDigital/subenum#329 ·
维护者通常 1 天内回复
-
[Bug] Backend summarize min() / max() panics when a field has no numeric values可能已有人在做 @weng5e 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 64/100
grafana/grafana-infinity-datasource#1832 ·
维护者通常 1 天内回复
-
tech-debt
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
GillMacedo/godebugdiff#13 ·