Conversation
# This is the 1st commit message: feat(schematics): allows wildcard in whitelisting of deep imports Formatted # This is the commit message nrwl#2: feat(schematics): allows wildcard in whitelisting of deep imports Formatted
Nx Cloud ReportCI ran the following commands for commit 5bfde7c. Click to see the status, the terminal output, and the build insights.
Sent with 💌 from NxCloud. |
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
The task nx:build-native failed because the Rust toolchain (specifically the cargo command) is not installed in the CI environment. The error message "cargo: not found" indicates a missing system dependency required to build native Rust components.
This failure is completely unrelated to the changes in this pull request. The PR updates Bazel build rules for Angular projects, modifying template files that configure how Angular applications and libraries are built with Bazel. These changes include:
- Migrating from deprecated
@build_bazel_rules_angularto the newer@angular/bazelpackage - Updating load paths and repository configurations
- Simplifying node_modules handling in BUILD.bazel files
- Adding Angular-specific compilation steps
None of these Bazel/Angular configuration changes would affect the availability of the Rust toolchain or the ability to compile Rust code in the packages/nx project. The nx:build-native task requires cargo to be present in the system PATH to compile Rust components, and this is an infrastructure/environment concern rather than a code issue.
The build environment needs to be configured with the Rust toolchain installed before this task can succeed. This is a pre-existing environment state issue that would affect any PR attempting to run the nx:build-native task, regardless of the code changes made.
A code change would likely not resolve this issue, so no action was taken.
⚙️ An Nx Cloud workspace admin can disable these reviews in workspace settings.
2 participants
No description provided.