apache / apache/maka

ci(windows): track remaining Release Windows check product failures

Open
#3,377 1 comment 0 reactions 0 assignees View on GitHub
help wanted
Dominant language
TypeScript
Stars
5.4k
Forks
502
Avg merge
1d 2h
Merged PRs (30d)
715

Description

English

## Purpose

#3327 made the Windows release verifier bounded and attributable without hiding product failures. This issue routes the remaining Windows release failures to one owner and stays open only while the current cross-cutting work is unresolved.

## Current status

| Item | Status | Ownership |
| --- | --- | --- |
| #3382 | Merged | Fixed the Runtime Host update handoff tracked by #3340. A recurrence of an old `ProductVersion`, surviving candidate, or busy install directory is a regression against this fix. |
| #3340 | Closed by #3382 | Historical issue for the update-handoff product defect. |
| #3348 | Closed and retired | Its raw-PID cleanup approach was removed because PID reuse cannot preserve process identity. It is not an active fix path. |
| #3265 | Open; checks green, independent review required | Adds installer Abort-path rollback and backup retention. It limits damage after a supported installer failure; it does not own Runtime Host startup failures. |
| #3279 | Open; primary remaining product fault | Owns intermittent `host_unresponsive` and renderer-never-mounted startup failures on Windows, including fresh isolated profiles. |
| #3327 | Merged | Owns only regressions in verifier deadlines, transient observation handling, cleanup barriers, or final evidence. |
| #2142 | Open roadmap | Tracks the broader work required to support Windows. |

## Triage

- Old executable version after update, a surviving Runtime Host candidate, or a busy install directory: file a focused regression referencing #3382.
- `Runtime Host stopped responding during startup`, `host_unresponsive`, or a renderer that never mounts: #3279.
- A probe exceeds its declared deadline, one transient observation aborts the run, or cleanup skips its final process/file/registry proof: file a focused verifier regression referencing #3327.
- Installer rollback or retained-backup behavior after Abort: #3265.

## Close when

- #3265 reaches a final disposition after independent human review.
- #3279 is independently reproduced and assigned a concrete fix path, or resolved.
- Any later Windows release failure can be handled in one focused owning issue rather than this cross-cutting router.

简体中文

## 目的

#3327 已经让 Windows release verifier 具备明确边界并能够提供可归因的证据,同时不会隐藏真实产品故障。本 issue 只负责把剩余 Windows release 失败分流到唯一责任项,并在当前跨问题工作收敛后关闭。

## 当前状态

| 项目 | 状态 | 职责 |
| --- | --- | --- |
| #3382 | 已合并 | 修复了 #3340 跟踪的 Runtime Host 更新交接问题。旧 `ProductVersion`、残留 candidate 或安装目录被占用再次出现时,应视为该修复的回归。 |
| #3340 | 已由 #3382 关闭 | 更新交接产品缺陷的历史 issue。 |
| #3348 | 已关闭并退役 | 其 raw-PID 清理方案无法在 PID reuse 下保证进程身份,已被删除,不再是有效修复路径。 |
| #3265 | 开放;检查全绿,待独立人工 review | 增加 installer Abort 路径的 rollback 与 backup retention,用于减轻受支持 installer 失败造成的损害;它不负责 Runtime Host 启动故障。 |
| #3279 | 开放;当前主要产品故障 | 负责 Windows 上间歇性的 `host_unresponsive` 和 renderer 始终未挂载问题,包括全新隔离 profile。 |
| #3327 | 已合并 | 只负责 verifier deadline、临时观测处理、清理屏障或最终证据方面的回归。 |
| #2142 | 开放路线图 | 跟踪 Windows 正式支持所需的更广泛工作。 |

## 分流规则

- 更新后仍是旧 executable 版本、存在残留 Runtime Host candidate 或安装目录被占用:创建聚焦的回归 issue,并关联 #3382。
- `Runtime Host stopped responding during startup`、`host_unresponsive` 或 renderer 始终未挂载:归 #3279。
- Probe 超出其声明 deadline、一次临时观测就中止整个 run,或清理跳过最终的进程/文件/registry 证明:创建聚焦的 verifier 回归 issue,并关联 #3327。
- Abort 后的 installer rollback 或 retained backup 行为:归 #3265。

## 关闭条件

- #3265 经过独立人工 review 后得到最终处理结论。
- #3279 被独立复现并获得明确修复路径,或已经解决。
- 后续 Windows release 失败可以归入单一、聚焦的责任 issue,而不再需要本跨问题路由器。

AI disclosure: OpenAI Codex updated and translated this maintainer-directed tracker after verifying the linked issues, pull requests, and current check state.

Contributor guide

Open the contributing guide

Research direction

This is a cross-cutting routing tracker rather than a self-contained code task. Read the linked issues #3265, #3279, #3327, and #3382, then use the triage rules to classify any new Windows release failure. The tracker is done when the listed issues have final dispositions and later failures can be assigned to one focused owning issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ci-cd, operating-systems, release
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.