Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Canceled
36883
7ed74177 chore(repo): record the traps in driving nx's TUI unattended Reproducing #36520 needed 160 unattended runs per version, and each of these cost an iteration before it was understood. - `tui.autoExit: 0` is a duration, so it means never auto-exit, not exit immediately. A loop set that way waits forever for a keypress. - 22.7.x keeps the TUI open after a task fails and `--tuiAutoExit=true` does not override it, so an unattended run hangs on exactly the case being measured. Feed it a quit. - `--tui` and `--outputStyle` are mutually exclusive; passing both prints help and exits 1, which reads as the reproduction failing. Also: size the pty, or the capability check refuses the TUI and the run measures the non-TUI path again.
by Craigory C...
Failed
36883
Fix ready→
1e28fa0a chore(repo): warn triage about the environment it reproduces in An arm that quietly exercises the absence of the feature under test comes back clean, and reads as a negative result. - `CLAUDECODE=1` makes `isAiAgent()` true, and `shouldUseTui()` returns false on it, so an agent-run TUI test is never on the TUI path. - A pty with no winsize refuses the TUI outright via the `columns > 0` check, which is how a hook runner's inner pty behaves. - Assert the state under test by calling the predicate or finding a byte-level tell, rather than inferring it from the command line. #36579 was measured twice on the non-TUI path before anyone checked.
by Craigory C...
Failed
36883
Fix ready→
4bc16154 chore(repo): hand the triage queue over in a side pane The agent and the reviewer work in parallel: records land while the reviewer is still deciding on earlier ones. That needs the TUI beside the conversation, not in front of it, and it needs decisions coming back without the agent polling. - Open `triage review` in a herdr or tmux split, self-closing on quit. - Arm watch-triage.sh as the return path: one line per status change with the reviewer's note, exiting once every record settles. It also reports if the state directory disappears mid-review, which a stray clean elsewhere in a shared checkout really can do. - Say plainly that this needs a multiplexer rather than degrading to a foreground TUI that takes the session over, or a detached one that exits immediately for want of a terminal. - Apply approvals as they arrive rather than at the end, so a reviewer who approves ten and steps away comes back to ten applied.
by Craigory C...
Failed
36883
Fix ready→
4bc16154 chore(repo): hand the triage queue over in a side pane The agent and the reviewer work in parallel: records land while the reviewer is still deciding on earlier ones. That needs the TUI beside the conversation, not in front of it, and it needs decisions coming back without the agent polling. - Open `triage review` in a herdr or tmux split, self-closing on quit. - Arm watch-triage.sh as the return path: one line per status change with the reviewer's note, exiting once every record settles. It also reports if the state directory disappears mid-review, which a stray clean elsewhere in a shared checkout really can do. - Say plainly that this needs a multiplexer rather than degrading to a foreground TUI that takes the session over, or a detached one that exits immediately for want of a terminal. - Apply approvals as they arrive rather than at the end, so a reviewer who approves ten and steps away comes back to ten applied.
by Craigory C...
Canceled
36883
4bc16154 chore(repo): hand the triage queue over in a side pane The agent and the reviewer work in parallel: records land while the reviewer is still deciding on earlier ones. That needs the TUI beside the conversation, not in front of it, and it needs decisions coming back without the agent polling. - Open `triage review` in a herdr or tmux split, self-closing on quit. - Arm watch-triage.sh as the return path: one line per status change with the reviewer's note, exiting once every record settles. It also reports if the state directory disappears mid-review, which a stray clean elsewhere in a shared checkout really can do. - Say plainly that this needs a multiplexer rather than degrading to a foreground TUI that takes the session over, or a detached one that exits immediately for want of a terminal. - Apply approvals as they arrive rather than at the end, so a reviewer who approves ten and steps away comes back to ten applied.
by Craigory C...
Failed
36883
Flaky task→
4bc16154 chore(repo): hand the triage queue over in a side pane The agent and the reviewer work in parallel: records land while the reviewer is still deciding on earlier ones. That needs the TUI beside the conversation, not in front of it, and it needs decisions coming back without the agent polling. - Open `triage review` in a herdr or tmux split, self-closing on quit. - Arm watch-triage.sh as the return path: one line per status change with the reviewer's note, exiting once every record settles. It also reports if the state directory disappears mid-review, which a stray clean elsewhere in a shared checkout really can do. - Say plainly that this needs a multiplexer rather than degrading to a foreground TUI that takes the session over, or a detached one that exits immediately for want of a terminal. - Apply approvals as they arrive rather than at the end, so a reviewer who approves ten and steps away comes back to ten applied.
by Craigory C...
Succeeded
36883
9ccaa2aa chore(repo): add the triage-issues skill A repo-facing workflow for triaging nrwl/nx issues: apply the labels that make an issue count as triaged, ask for a reproduction when one is missing, run it when one exists, and propose a priority and an owner. Every mutation is staged through .claude/tools/triage for a human to approve; the skill never writes to GitHub itself. The definition of "triaged" is not a convention here. Any open issue with no `scope:` label increments untriagedIssueCount in scripts/issues-scraper/scrape-issues.ts, which issue-notifier.yml posts to Slack weekly, so the queue query mirrors that scraper exactly. Things the skill encodes because they are easy to get wrong: - A `blocked:` label is an eviction timer, not a note. schedule-stale.yml gives 7 days to `stale` and 21 more to closed. Removing one when the reporter answers is a triage duty, since the bot only strips `stale`. - `stale` and `outdated` are bot-owned and must never be set by hand. - closedByPullRequestsReferences finds a PR already in flight, including on open issues. Scraping /timeline for cross-referenced events does not. - The scope table is built from how maintainers actually label, not from the label descriptions: `scope: bundlers` reads "webpack, rollup" but covers vite, esbuild, rspack and rsbuild too. - A `Steps to Reproduce` section containing only `1.` is the bug form's seeded default, not a reproduction. No labels at all means the issue was filed outside the form, so none of its required fields are guaranteed. - Before proposing `community`, check the fix is contributable. The repo does ship graph UI source under graph/, but those packages import the published closed-source @nx/graph, so "it's a graph bug" decides nothing. references/labels.md holds the scope map and close reasons; references/replies.md holds comment templates.
by Craigory C...
Failed
36883
Fix applied→
9ccaa2aa chore(repo): add the triage-issues skill A repo-facing workflow for triaging nrwl/nx issues: apply the labels that make an issue count as triaged, ask for a reproduction when one is missing, run it when one exists, and propose a priority and an owner. Every mutation is staged through .claude/tools/triage for a human to approve; the skill never writes to GitHub itself. The definition of "triaged" is not a convention here. Any open issue with no `scope:` label increments untriagedIssueCount in scripts/issues-scraper/scrape-issues.ts, which issue-notifier.yml posts to Slack weekly, so the queue query mirrors that scraper exactly. Things the skill encodes because they are easy to get wrong: - A `blocked:` label is an eviction timer, not a note. schedule-stale.yml gives 7 days to `stale` and 21 more to closed. Removing one when the reporter answers is a triage duty, since the bot only strips `stale`. - `stale` and `outdated` are bot-owned and must never be set by hand. - closedByPullRequestsReferences finds a PR already in flight, including on open issues. Scraping /timeline for cross-referenced events does not. - The scope table is built from how maintainers actually label, not from the label descriptions: `scope: bundlers` reads "webpack, rollup" but covers vite, esbuild, rspack and rsbuild too. - A `Steps to Reproduce` section containing only `1.` is the bug form's seeded default, not a reproduction. No labels at all means the issue was filed outside the form, so none of its required fields are guaranteed. - Before proposing `community`, check the fix is contributable. The repo does ship graph UI source under graph/, but those packages import the published closed-source @nx/graph, so "it's a graph bug" decides nothing. references/labels.md holds the scope map and close reasons; references/replies.md holds comment templates.
by Craigory C...