Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  feat/nxc-4901-daemon-v8-framing
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

fix(core): pin NX_MAX_MESSAGE_SIZE to the daemon spawn env The daemon's parser reads the message-size limit when a connection is accepted, before the connecting client's env is applied, so reflecting NX_MAX_MESSAGE_SIZE into the daemon let one client's value govern the next client's connection while never governing its own. Exclude it from env reflection and carry it in the spawn env instead: the limit is now pinned for the daemon's lifetime and a change takes effect via nx reset, which the refusal error message and docs now say. Also stop watcher redials after 3 consecutive framing failures instead of 4, matching MAX_CONSECUTIVE_FRAMING_FAILURES, and correct two comments: describeMessage's utf8 rationale (valid multi-byte sequences decode fine; the v8 header is what can never decode) and a spec comment that misstated the old string-prefix classifier's gap. Claude-Session: https://claude.ai/code/session_01C9PcGMvRo2sGXLgf1uu9hY

nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte

Succeeded

4 CPU cores

read-write access token used

ebee702e36838

Get faster results

Learn how to enable distribution.

Atomizer enabled

1 group of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace