Skip to content

Conversation

@leosvelperez
Copy link
Member

Add a new NX_MIGRATE_SKIP_REGISTRY_FETCH environment variable to opt out of fetching package versions and migrations metadata from the registry and instead, use package installation to get the information.

@leosvelperez leosvelperez self-assigned this Sep 25, 2025
@leosvelperez leosvelperez requested review from a team as code owners September 25, 2025 15:48
@vercel
Copy link

vercel bot commented Sep 25, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
nx-dev Ready Ready Preview Sep 25, 2025 4:20pm

@nx-cloud
Copy link
Contributor

nx-cloud bot commented Sep 25, 2025

View your CI Pipeline Execution ↗ for commit 492c374

Command Status Duration Result
nx affected --targets=lint,test,test-kt,build,e... ✅ Succeeded 8m 51s View ↗
nx run-many -t check-imports check-commit check... ✅ Succeeded 2m 32s View ↗
nx-cloud record -- nx-cloud conformance:check ✅ Succeeded 3s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 3s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded <1s View ↗
nx documentation ✅ Succeeded 13s View ↗

☁️ Nx Cloud last updated this comment at 2025-09-26 07:46:35 UTC

Copy link
Contributor

@nx-cloud nx-cloud bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud has identified a possible root cause for your failed CI:

The failure is classified as 'environment_state' because it is caused by an environmental issue rather than the code changes in this pull request.

Analysis of the failure:

The test failure occurs with the error message:

Command failed: npx playwright install --with-deps
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 24753 (apt-get)
E: Unable to lock directory /var/lib/apt/lists/

This is a clear environmental failure where:

  1. The system package manager (apt) is already running or locked by another process
  2. This prevents Playwright from installing system dependencies with --with-deps
  3. The error is related to Linux system package management, not the code changes

Why this is not related to the PR changes:

The PR changes involve:

  • Adding a new environment variable NX_MIGRATE_SKIP_REGISTRY_FETCH
  • Updating documentation to describe this variable
  • Adding logic in migrate.ts to check this environment variable and skip registry fetching

These changes have no relationship to:

  • Playwright browser installation
  • System package management
  • APT lock conflicts
  • E2E test environment setup

Evidence this is environmental:

  • The error occurs during Playwright browser installation, which is an environmental setup step
  • APT lock conflicts are classic environmental issues in CI systems
  • The same test appears to have passed in other parts of the test suite, indicating the issue is intermittent and environmental
  • No similar failures are present in the <similar_task_failures> section, suggesting this is a transient environmental issue

The failure is unrelated to the pull request's code changes and represents a temporary system-level resource contention issue.

A code change would likely not resolve this issue, so no action was taken.

Nx CloudView in Nx Cloud ↗


⚙️ An Nx Cloud workspace admin can disable these reviews in workspace settings.

@leosvelperez leosvelperez merged commit 6c109d2 into master Sep 26, 2025
16 of 17 checks passed
@leosvelperez leosvelperez deleted the core/migrate-disable-metadata-from-registry branch September 26, 2025 12:10
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2025

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants