Repository navigation
test: qualify 3.5.2 SPA with isolated services [skip deploy] - #175
Conversation
|
3.5.2 SPA补验合并前报告：PR175最终HEAD 9499e62；CI39018356165 成功，CLEAN/MERGEABLE。此PR只有验收夹具/证据，CI实际运行changes，checks/integration/publish及部署按路径SKIPPED，不把跳过说成执行了浏览器。 云环境实际owning验证：完整React SPA6/6、零失败/重试/跳过；隔离保护2/2（先红后绿）、既有fixture-safety3/3、E2E类型检查及全新构建通过。13截图、6视频、真实消息计数、Web生命周期、构建hash与37文件manifest已保留。逐项验收映射与证据。 复核153/155/157/161未发现额外产品/runtime代码缺口。可独立完成的会话/发送/网络/DB/Web故障SPA已跑完。完整Worker所需相同bwrap预检：当前执行器uid-map只读，独立容器不能创建namespace，均exit1；未扩权。真实provider/prices环境五项均未提供，只记录存在性、不输出值。剩余是合格Worker/授权provider和价格/完整观察时窗；3.5.2耐久未验证，不用旧soak替代。 原3.5.1 soak monitor285092、watcher363050保持运行且候选镜像restart0、原起始时间不变。新SPA独立服务已清理。既有名为“LingxiLoop soak复查”的单次任务已确认启用，2026-10-18 06:50UTC读取公开远端回执/心跳；没有重复创建，任务标识已在私有交接中提供。 现按原授权普通合并PR175，明确使用[skip deploy]；不部署、不探测Komodo、不改生产安全配置。 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
2 participants
Qualify the actual freshly built React SPA against published runtime3.5.2 while the original3.5.1 soak continues. The previous acceptance helper paused a shared PostgreSQL container; add a fixed isolated profile with separate PG/Redis/WuKongIM/storage, Web/control/runtime ports and D1 state. Database pause verifies the exact disposable container label and loopback binding; unknown profiles fail closed.
Cloud owning results: 6/6 full-SPA cases, zero failures/retries/skips, including session restore/reload/expiry/renewal, network abort, actual independent PostgreSQL pause/unpause, actual Web stop/start and both expired-session send races. Successful sends retain one acceptance and one actual WuKong message; rejected old sends remain unsent after renewal and the next send succeeds. Safety tests were red before the change and pass2/2; existing fixture safety3/3, E2E typecheck and fresh React build pass.
Retained evidence: 13 screenshots,6 videos, exact message counts, Web lifecycle, all build-asset hashes, container identities and37-file SHA256 manifest. Product source is main
ba9014958f7ab0dc0636a18edd1339d9e9e76e60; the executed unchanged harness isac7f9d4b2e5179de6c438ac8c5db9ae9b5d3fb15. The runner's dirty-start VCS fact is retained. No product code changed.The exact Worker bubblewrap preflight fails on this executor (
setting up uid map: Read-only file system, exit1) and in a separate default-security/no-network diagnostic container (No permissions to create new namespace, exit1). The second probe reads the exact registry3.5.2 public version export through a read-only package mount; it is explicitly not an immutable3.5.2 image/full Worker qualification. No security configuration, privilege or credential was changed.Read-only review of153/155/157/161 found no additional product/runtime code gap. The mapping retains external provider/pricing/approved-route, qualified full Worker and complete observation-window conditions. This qualifies post-login SPA session/human messaging, not captcha, live model answers or3.5.2 endurance. Original3.5.1 monitor285092/watcher363050 remain running; the already-enabled one-time06:50UTC follow-up was verified, with no duplicate task. Independent test services were stopped afterwards.
Harness/docs-only scoped CI may run only
changesand skip product suites; the results above are actual cloud owning executions, not claims about skipped jobs. Merge normally with[skip deploy]; no production deployment or Komodo probe.