Overview - Nx

Your Enterprise license expires in 16 days.

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
373
26925c2e refactor(schematics): rename ast json methods more explicitly
11 hours ago by FrozenPandaz
Succeeded
578
b9393d41 fix(schematics) affect a project by deleting a file
15 hours ago by FrozenPandaz
Failed
34148
Fix ready→
e5cba863 fix(testing): add timeout to runCommandUntil to prevent hanging tests Add a configurable timeout (default 5 seconds) to the runCommandUntil e2e utility function. Previously, if the expected output never appeared, the function would wait indefinitely, causing CI jobs to hang for hours. The timeout can be customized via opts.timeout for tests that need more time to start up.
15 hours ago by FrozenPandaz
Failed
34148
Fix available→
fae8d6f8 fix(testing): add timeout to runCommandUntil to prevent hanging tests Add a configurable timeout (default 5 seconds) to the runCommandUntil e2e utility function. Previously, if the expected output never appeared, the function would wait indefinitely, causing CI jobs to hang for hours. The timeout can be customized via opts.timeout for tests that need more time to start up.
16 hours ago by FrozenPandaz
Canceled
34138
fdfda6b2 Merge branch 'master' into upnx
20 hours ago by FrozenPandaz
Succeeded
577
d602adf6 feat(schematics) add migration for implicitDependencies
2 days ago by FrozenPandaz
Succeeded
372
0cdac278 refactor(schematics): add method for updating and reading json
2 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
576
79327c35 feat(schematics): allow isolation of failed affected commands
3 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Canceled
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Failed
master
6754cde0 fix(core): drain stdin on exit to prevent escape sequence leakage (#34134) ## Current Behavior When exiting the TUI (especially via Ctrl+C), escape sequences leak to the terminal: ``` ^[]11;rgb:2121/2121/2121^[\^[[55;1R^[[?62;22;52c ``` This happens because the TUI queries terminal background color via OSC 11 to detect dark/light mode. The terminal responds with an escape sequence, but if the program exits before fully consuming the response, it appears in the terminal output. ## Expected Behavior Clean terminal state after TUI exits, with no escape sequence artifacts. ## Related Issue(s) N/A - discovered during development ## Solution Added `drain_stdin()` function that polls and consumes any pending terminal events before disabling raw mode. This clears any lingering OSC responses (like the background color query response) before the terminal is restored. ```rust fn drain_stdin() { use std::time::Duration; while crossterm::event::poll(Duration::from_millis(5)).unwrap_or(false) { let _ = crossterm::event::read(); } } ``` The 5ms timeout is long enough to catch pending responses but short enough not to noticeably delay exit.
3 days ago by FrozenPandaz
Succeeded
34134
3fa9ba20 fix(core): prevent RGB escape sequence leakage and handle 0x0 terminal size - Add drain_stdin() to consume pending terminal responses (OSC color queries) before TUI exit, preventing escape sequences from leaking to terminal - Disable TUI when terminal reports 0x0 size to prevent vt100 parser panics - Add graceful fallback for inline terminal creation errors
3 days ago by FrozenPandaz
Succeeded
master
4202f2c7 fix(core): prevent task hashing when project graph has errors (#34116) ## Current Behavior When the daemon encounters a project graph error during task hashing, it extracts the partial project graph from the error and continues hashing tasks. This can produce incorrect hashes since the graph is incomplete. ## Expected Behavior The error should be thrown immediately, preventing any hashing attempts with an invalid project graph. This ensures we don't produce incorrect task hashes that could lead to cache issues. ## Related Issue(s) N/A - Bug fix discovered during development
3 days ago by FrozenPandaz
Succeeded
master
4202f2c7 fix(core): prevent task hashing when project graph has errors (#34116) ## Current Behavior When the daemon encounters a project graph error during task hashing, it extracts the partial project graph from the error and continues hashing tasks. This can produce incorrect hashes since the graph is incomplete. ## Expected Behavior The error should be thrown immediately, preventing any hashing attempts with an invalid project graph. This ensures we don't produce incorrect task hashes that could lead to cache issues. ## Related Issue(s) N/A - Bug fix discovered during development
3 days ago by FrozenPandaz
Succeeded
master
4202f2c7 fix(core): prevent task hashing when project graph has errors (#34116) ## Current Behavior When the daemon encounters a project graph error during task hashing, it extracts the partial project graph from the error and continues hashing tasks. This can produce incorrect hashes since the graph is incomplete. ## Expected Behavior The error should be thrown immediately, preventing any hashing attempts with an invalid project graph. This ensures we don't produce incorrect task hashes that could lead to cache issues. ## Related Issue(s) N/A - Bug fix discovered during development
3 days ago by FrozenPandaz