fix(core): display bottom corner indicator of tui in progress section correctly

[leosvelperez]

Current Behavior

The bottom corner indicator of the in-progress section in the TUI is not displayed when there are more tasks in progress than the maximum parallel capacity (this can occur when there are continuous tasks).

Expected Behavior

The bottom corner indicator of the in-progress section in the TUI should always be displayed at the end of the running tasks.

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	c7ead7d
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/68e4da6cfd1573000824aeeb
😎 Deploy Preview	https://deploy-preview-32985--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vercel]

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

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Oct 7, 2025 9:27am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit c7ead7d

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

---

☁️ Nx Cloud last updated this comment at 2025-10-07 11:18:14 UTC

[nx-cloud]

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

The pull request modifies Rust code in the Nx TUI component (packages/nx/src/native/tui/components/tasks_list.rs) to fix a visual rendering bug where the bottom corner indicator is not displayed correctly. The change adjusts the separator calculation logic to account for scenarios where more tasks are in progress than the configured parallel limit.

All four failing e2e tests exhibit identical environmental failures during package installation:

• e2e-angular fails with ERR_PNPM_FETCH_404 for lodash
• e2e-esbuild tests fail with ERR_PNPM_FETCH_404 for glob-to-regexp and immutable
• e2e-react fails with connection refused errors (cascading from setup failures)

These failures are categorized as 'environment_state' because:

1. The local npm registry at localhost:4873 is failing to serve required packages
2. The errors are network-related (ERR_PNPM_FETCH_404, "Not Found - 404")
3. There is zero logical connection between Rust TUI rendering code changes and npm package resolution
4. The PR only modifies visualization logic for the terminal interface
5. These appear to be transient registry issues unrelated to any code changes

The test failures are caused by infrastructure issues with the local npm registry used for e2e testing, not by the code changes in this pull request. The changes to the TUI rendering logic are isolated to the Rust codebase and cannot affect package installation behavior.

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

View in Nx Cloud ↗

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