mirror of
https://github.com/codewhale-hq/Codewhale.git
synced 2026-11-08 17:10:50 -10:00
CodeWhale Bot
c0c7998188
Two release-candidate artifact jobs failed on0d1ffc1cb2, and neither was a product defect. ohos-arm64: the SDK mirror publishes the C++ `toolchains/lib/binary-sign-tool` and no `binary-sign-tool.jar`, so the signer probe failed after the binary had already cross-compiled in 27m33s ("binary-sign-tool.jar is missing from the SDK toolchains component"). I extracted the pinned SDK archive and confirmed the layout and the tool's own usage text: the native binary takes the same `sign` / `display-sign` subcommands and the same `-inFile` / `-outFile` / `-selfSign` flags. The step now uses the jar when a DevEco SDK provides one and the native tool otherwise, and lists `toolchains/lib` when neither exists. windows-x64: the build, the import check and the version banner all passed (`codewhale 0.10.3 (0d1ffc1cb2)`); the clipboard acceptance harness died with `TimeoutError` before it ever spawned a terminal, so the receipt carried no desktop state. The retry loop added earlier only retried the response headers — `fetch`'s 60s signal also covers the body read, so a slow 200 timed out on `arrayBuffer()`. The retry now covers fetch + body + digest as one unit with a 180s budget per attempt. Verification: node --test .github/scripts/release-workflows.test.js → pass (the OHOS step contract still asserts the jar path, -selfSign 1, display-sign ordering and scripts/ohos-env.sh); node --check on the harness. Neither fix has run on a hosted runner yet; that is what the next RC dispatch is for.