Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36924
73a75548 fix(core): restore the wasm walker imports dropped by a stray cfg attribute
by Craigory C...
Canceled
36924
c18fcabc chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Canceled
36924
55007755 chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Canceled
36924
1daba8aa chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Succeeded
fix/wasm-walker-cfg-imports
bed2d10e chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Succeeded
36924
3ecc53f2 chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Succeeded
fix/wasm-walker-cfg-imports
7527f4a1 chore(repo): check the wasm target on PRs that touch rust Nothing in PR CI compiled for wasm32, so a break there sat on master until `pnpm build:wasm` ran at publish time. That is how the walker.rs cfg regression shipped. A full wasm build needs the wasi-sdk tarball, cmake and the sqlite C flags, which is too much for every PR. `cargo check` never links, so it needs none of that, just the nightly toolchain, the target, and EMNAPI_LINK_DIR pointing into node_modules. It still catches this class of bug, since E0599 is a resolution error. The job runs on every PR but gates its expensive steps behind a git diff for `.rs`/`Cargo.*`/`rust-toolchain.toml`, the same shape as the React Native check on main-macos, so it still reports a status on unrelated PRs.
by Craigory C...
Canceled
36924
d589c665 fix(core): restore the wasm walker imports dropped by a stray cfg attribute `#[cfg(...)]` binds to the single item that follows it. In walker.rs that item was the `enable_logger` import, and removing it in #36895 re-homed the attribute onto the `utils` import below, gating `Normalize`, `get_mod_time` and `parent_gitignore_files` out of the wasm32 build. All three are still used there: the wasm `nx_walker` calls `to_normalized_string` and `get_mod_time`, and `create_walker` — shared by both targets — calls `parent_gitignore_files`. None of them need gating. Verified `cargo check -p nx` and `cargo check -p nx --target wasm32-wasip1-threads` both pass.
by Craigory C...
Canceled
36924
d589c665 fix(core): restore the wasm walker imports dropped by a stray cfg attribute `#[cfg(...)]` binds to the single item that follows it. In walker.rs that item was the `enable_logger` import, and removing it in #36895 re-homed the attribute onto the `utils` import below, gating `Normalize`, `get_mod_time` and `parent_gitignore_files` out of the wasm32 build. All three are still used there: the wasm `nx_walker` calls `to_normalized_string` and `get_mod_time`, and `create_walker` — shared by both targets — calls `parent_gitignore_files`. None of them need gating. Verified `cargo check -p nx` and `cargo check -p nx --target wasm32-wasip1-threads` both pass.
by Craigory C...
Canceled
36924
d589c665 fix(core): restore the wasm walker imports dropped by a stray cfg attribute `#[cfg(...)]` binds to the single item that follows it. In walker.rs that item was the `enable_logger` import, and removing it in #36895 re-homed the attribute onto the `utils` import below, gating `Normalize`, `get_mod_time` and `parent_gitignore_files` out of the wasm32 build. All three are still used there: the wasm `nx_walker` calls `to_normalized_string` and `get_mod_time`, and `create_walker` — shared by both targets — calls `parent_gitignore_files`. None of them need gating. Verified `cargo check -p nx` and `cargo check -p nx --target wasm32-wasip1-threads` both pass.
by Craigory C...
Canceled
36924
d589c665 fix(core): restore the wasm walker imports dropped by a stray cfg attribute `#[cfg(...)]` binds to the single item that follows it. In walker.rs that item was the `enable_logger` import, and removing it in #36895 re-homed the attribute onto the `utils` import below, gating `Normalize`, `get_mod_time` and `parent_gitignore_files` out of the wasm32 build. All three are still used there: the wasm `nx_walker` calls `to_normalized_string` and `get_mod_time`, and `create_walker` — shared by both targets — calls `parent_gitignore_files`. None of them need gating. Verified `cargo check -p nx` and `cargo check -p nx --target wasm32-wasip1-threads` both pass.
by Craigory C...