fix(cli): avoid O(n²) spinner truncation in CI

[ADITYA-CODE-SOURCE]

Summary

• return the original spinner message when stdout is not a TTY or has no column width so CI does not pay truncation costs
• replace the repeated rescan loop in truncateMessage() with a single-pass ANSI-aware truncation path
• add CLI utility tests for non-TTY behavior plus ANSI and terminal hyperlink truncation

Testing

• corepack pnpm --filter trigger.dev test src/utilities/windows.test.ts

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26277a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0842268f-2be1-462c-8e72-bb082057818b

📥 Commits

Reviewing files that changed from the base of the PR and between e092919 and 26277a8.

📒 Files selected for processing (2)

• packages/cli-v3/src/utilities/windows.test.ts
• packages/cli-v3/src/utilities/windows.ts

---

Walkthrough

windows.ts replaces its previous iterative slice-and-remeasure truncation with a stateful, single-pass character-walking implementation. New regex patterns and an ANSI-state tracker are introduced to compute visible string length while ignoring ANSI escape sequences and terminal hyperlink sequences. The truncation loop accumulates encountered escape sequences, tracks whether SGR color/style or terminal hyperlink sequences remain open at the truncation boundary, and conditionally appends the appropriate closing hyperlink escape and ANSI reset before the trailing ellipsis. windows.test.ts is added as a new file containing a Vitest suite that mocks process.stdout.isTTY and process.stdout.columns, restores both after each test, and covers all truncation paths including non-TTY passthrough, missing column width, short strings, plain-string truncation, ANSI-colored strings, and hyperlink preservation.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Hi @ADITYA-CODE-SOURCE, thanks for your interest in contributing!

This project requires that pull request authors are vouched, and you are not in the list of vouched users.

This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details.

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🟡 updateAnsiState ignores previous SGR state on partial resets, causing terminal attribute leaks

updateAnsiState accepts a hasActiveSgr parameter but never uses it when the sequence ends with m (line 24). It only checks whether the current sequence's codes are non-reset codes. When a partial reset is encountered (e.g. \x1b[39m to reset foreground), the function returns false even if other attributes (e.g. bold from a prior \x1b[1;31m) are still active.

Example trace showing the bug

For input \x1b[1;31mhe\x1b[39mllo world with truncation at 4 visible chars:

1. \x1b[1;31m → codes=[1,31], 1 not in resetCodes → hasActiveSgr = true ✓
2. 'h','e' → visible chars
3. \x1b[39m → codes=[39], 39 IS in resetCodes → codes.some(code => !ansiResetCodes.has(code)) returns false → hasActiveSgr = false ✗
4. 'l','l' → 4 visible chars reached, truncate
5. hasActiveSgr is false → no \x1b[0m appended

Result: \x1b[1;31mhe\x1b[39mll... — bold (code 1) leaks into subsequent terminal output.

The fix should consult hasActiveSgr when all codes in the current sequence are reset codes but none is a full reset (code 0). Only a full reset (\x1b[0m) or explicit reset of every active attribute should clear the state.

Suggested change

	return codes.some((code) => !ansiResetCodes.has(code));
	if (codes.some((code) => !ansiResetCodes.has(code))) return true;
	if (codes.includes(0)) return false;
	return hasActiveSgr;

---

Was this helpful? React with 👍 or 👎 to provide feedback.