Repository navigation
main CI debt: docs-quality, ts-noemit, Clean Room (landlock), cross-check, strict-block-ga failing on main #102
Description
Several CI checks are failing on main itself (HEAD 89d0493bc5cf87373ced354eb1f3b6624a707626), independent of any PR. They surface on every PR that merges main (e.g. #98) but are not caused by those PRs. Filing one consolidated tracker so they're owned and visible. All are advisory (PRs show UNSTABLE, not BLOCKED).
Verification method: queried repos/vox-foundation/vox/commits/<main-HEAD>/check-runs, and for each, confirmed the implicated files are not in #98's diff (git diff origin/main...HEAD) and/or the relevant source is unchanged by recent commits.
1. Clean Room Setup + Idempotency (ubuntu/macos/windows) — confirmed failure on main HEAD
cargo build during setup.vox provision fails with E0308 in crates/vox-cli/src/commands/runtime/run/sandbox.rs (lines 53/59/64/68/76): expected AccessFs, found BitFlags<AccessFs, u64>. A Landlock (landlock/enumflags2) API mismatch in Linux-only code. Needs a fix by someone who can build for Linux + knows the pinned landlock version.
2. vox audit --gate all --strict-block-ga — confirmed failure on main HEAD
The aspirational block-GA gate is red on main.
3. ts-noemit (TS emit typecheck)
Emitted __emit_test__ TS fails tsc --noEmit: Cannot find module '@vox/runtime'; Property 'initial' missing in TimerProps; ErrorBoundary.setState incompatible with base Component. The codegen emitter (crates/vox-codegen/src/codegen_ts/) is unchanged in main's recent commits; path-gated so it only runs when codegen/compiler paths change.
4. cross-check (macos-latest aarch64-apple-darwin, windows x86_64) — path-gated
Cross-compilation of the workspace (incl. the new mobile crates). Not reproduced here.
5. docs-quality (Starlight build) — confirmed failure on main HEAD
A chain of content-collection schema violations in main-authored docs. One class fixed in #98 (unquoted last_updated YAML dates → parsed as Date, fails z.string() — quoted 5 mobile docs). Remaining: architecture/_screenshots/research-sources.md + multiple Failed to parse Markdown (golden.md, tutorials/, reference/, how-to/*).
Recommendation: fix each in its owning subsystem's PR. These should not gate unrelated PRs; consider marking the chronically-red advisory checks non-required until addressed. Discovered while landing #98 (harness follow-ups), whose own CI concerns are green.
Activity
brbrainerd commentedon Jun 1, 2026
Update — root cause of
cross-check(#4) pinnedcross-platform-check.ymlrunscargo check --workspace --target <triple>with no GUI-frontend build step.crates/vox-guiis a Tauri bin whosetauri::generate_context!()(main.rs:103) readstauri.conf.jsonat compile time and requiresfrontendDist = "ui/dist"to exist.crates/vox-gui/ui/distis gitignored (0 tracked files), so on a fresh runner the macro fails:This blocks both
cross-check (windows)andcross-check (macos)forvox-gui. It's environmental/pre-existing (not a code regression; reproduces only whenui/distis absent).vox-gui's Rust otherwise compiles cleanly cross-platform.Recommended fix (workflow-policy decision for the owner):
--exclude vox-guito the cross-check command — the Tauri bin can't becargo checked without a built frontend, and its Rust is already exercised by the host CI build.pnpm -C crates/vox-gui/ui install && pnpm -C crates/vox-gui/ui build) beforecargo check, soui/distexists. Heavier (adds node/pnpm setup + build time to a "quick" cross-check).Note (separate, already fixed in #98): a real regression —
vox-guiwas missing atracingdep for newly-addedtracing::debug!calls — sat in front of thisfrontendDisterror and is now resolved.brbrainerd commentedon Jun 1, 2026
Update:
cross-check(#4) addressed in PR #98 via Option A —cargo check --workspace --exclude vox-gui ...(commit 4bf25c8). The Tauri bin can't be cargo-checked without a built frontend, and its full build is covered by release-gui.yml. Verified locally:cargo check --workspace --exclude vox-gui --target x86_64-pc-windows-msvc→ RC=0. The remaining four items in this issue (strict-block-ga, docs-quality, Clean Room/landlock, ts-noemit) are still open and owner-assigned.fix(codegen): align list-HOF fold emit test with into_iter value sema…
brbrainerd commentedon Jun 13, 2026
Docker reproduction on current main (2026-06-13) — most of these are already resolved
Ran each failing check inside the
vox-ci-runner-localLinux image (Rust 1.96 + Node 24 + pnpm) against currentorigin/main:cargo check -p vox-cli, the E0308 in sandbox.rs)pnpm buildlangswarnings forpwsh/gitignore/envfenced blocks)vox ci doctest-md --strictvox ci canonical-map-verifycargo check --target x86_64-pc-windows-msvcaws-lc-sysneeds NASM + the MSVC toolchain/libs; runs natively onwindows-latestin CI. Also:cross-platform-checkwas moved to weekly-only / non-required in #279, so it no longer gates PRs or the merge queue.aarch64-apple-darwinConclusion: the Linux-side debt (landlock + docs-quality) is already green on current main — this issue was tracking a stale state. The only remaining items are the cross-platform native checks, which (a) can't be reproduced off their native OS and (b) are no longer per-PR gates. Recommend narrowing or closing this issue once a native cross-platform run confirms green. (ts_emit typecheck not re-run here — flag if still red on the native CI.)
Cosmetic follow-up (optional): register
pwsh/gitignore/gitattributes/envindocs-astro/astro.config.mjsshikilangsto silence the build warnings.