nxNx
GitHubNxWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      examples/dotnet-openapi-typescript
    • Runs and Agents
    • Timeline
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
  • Sign in
    fix(repo): exclude the dotnet example's bin/obj reads too The writes exclusion landed, but `validate-example` then failed with 131 unexpected reads, all of them the same bin/ and obj/ files the task had just written: restore writes obj/project.assets.json for the build to consume, and the test run loads its assemblies out of bin/. They are this task's own scratch in both directions, so the exclusion applies to reads as well. Anchored so the two lists cannot drift apart. Confirmed from the sandbox report: 87 reads under tests/Catalog.Tests/bin, 16 under tests/Catalog.Tests/obj, 14 under libs/Catalog/obj, 11 under apps/Api/obj and 3 under libs/Catalog/bin. Nothing outside bin/ or obj/.
    nx affected --targets=lint,oxlint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example
Succeeded
read-write access token used
70117b4536701
85%

Cache hits

719 of 846 tasks used cache.

91%

Distribution saved time

16m 44s instead of 2h 59m 46s.

Atomizer enabled

49 groups of tasks optimized.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools