patchrail 0.2.0__tar.gz → 0.3.0__tar.gz

{patchrail-0.2.0 → patchrail-0.3.0}/.gitignore

@@ -1,4 +1,6 @@
 .venv/
+.venv*/
+venv/
 .DS_Store
 .pkg-smoke/
 .patchrail-release-smoke/

patchrail-0.3.0/CHANGELOG.md

@@ -0,0 +1,217 @@
+# Changelog
+
+## 0.3.0 - 2026-07-09
+
+### Fixed
+
+- Deterministic Go test failures are no longer misread as
+  `network_transient_failure` when their logs contain incidental
+  network-shaped noise (`dial tcp`, `connection refused`, `context deadline
+  exceeded`, `i/o timeout`). The classifier now defers a broad transient-network
+  match built *entirely* from these ambiguous signals to the concrete failure
+  when one also matched, so a real bug isn't mislabeled "just retry". Genuine
+  outages still classify as transient because they trip a terminal signal (DNS
+  resolution, rate limit, gateway error, TLS handshake, or a git remote hang-up)
+  outside the ambiguous set. `go_test_failure` also now recognises the canonical
+  `--- FAIL:` marker. New `go-integration-test-network-noise` fixture guards this,
+  bringing the benchmark zoo to 208 cases.
+
+### Added
+
+- `patchrail --version` now prints the installed version (e.g. `patchrail 0.3.0`)
+  and exits, so a maintainer can confirm which release they are running without
+  invoking a subcommand.
+- `java_build_failure` now also recognises **sbt** (Scala on the JVM). sbt prints
+  none of the Maven/Gradle banners the rule keyed on, so a genuine
+  `(project / Test / compileIncremental) Compilation failed` — or an
+  `sbt.TestsFailedException` — previously fell through to `unknown`. New signals
+  cover the sbt session banner, incremental-compile failure, Scala
+  `not found: value`/`not found: type` errors, and the sbt test-failure
+  exception; the reproduction command now suggests `sbt test`. New sanitized
+  `github-actions-sbt-scala-compile` fixture (modelled on a real
+  `scalatest/scalatest` GitHub Actions run) guards this, bringing the benchmark
+  zoo to 209 cases.
+- New sanitized `ruby-rspec-parallel-failure` fixture captures a real
+  `rubocop/rubocop` RSpec failure tail (parallel/turbo_tests summary with
+  `pending` before `failures`), bringing the benchmark zoo to 207 cases.
+- New `xcode_build_failure` class classifies Apple-platform build and test
+  failures from `xcodebuild`, `swift build`/`swift test`, and Swift Package
+  Manager — Swift compile errors, missing modules (`error: no such module`),
+  unresolved package dependencies, and XCTest failures (`** BUILD FAILED **`,
+  `** TEST FAILED **`, `The following build commands failed:`). Backed by three
+  sanitized fixtures in `examples/ci-triage/`, bringing the benchmark zoo to 169
+  cases and the classifier to 40 failure classes.
+- New `docs_build_failure` class classifies documentation-site build failures
+  from Sphinx (`sphinx-build -W` warnings-as-errors, missing toctree entries),
+  MkDocs (`mkdocs build --strict` broken links), and Docusaurus (`docusaurus
+  build` broken links). Backed by three sanitized fixtures in
+  `examples/ci-triage/`, bringing the benchmark zoo to 166 cases.
+- `patchrail ci classes` lists every supported failure class with its likely
+  subsystem and reproduction command (plus the `unknown` fallback), in stable
+  order. Supports `--format text|json|markdown` and `--out`, so the set of
+  classes the classifier can diagnose is discoverable from the CLI instead of
+  only in the source. Closes #150.
+
+### Fixed
+
+- Real RSpec failures now classify as `ruby_bundle_failure` instead of
+  `unknown`. RSpec prints its rerun list as `rspec ./path/to/thing_spec.rb[…]`
+  and its summary as `N examples, [K pending, ]M failures` (rspec, parallel and
+  turbo_tests) — neither of which the old `rspec .*failures?` pattern matched,
+  so a pasted spec-failure tail without bundler setup lines fell through to
+  `unknown`. Two shape-matching patterns were added to the rule. Surfaced by
+  dogfooding a real `rubocop/rubocop` CI run.
+- Python CI logs no longer misclassify as `python_dependency_resolution` just
+  because they run `python -m pip install`. That bare command line was a
+  detection pattern, but it appears in almost every Python CI job regardless of
+  what actually failed, so any failing Python job with no stronger signal was
+  reported as a dependency-resolution conflict with the misleading "pin or relax
+  the conflicting dependency range" advice. Dogfooded against a real
+  `pandas-dev/pandas` 32-bit CI run whose `pip install` failed at
+  `metadata-generation-failed` (a package build error, `Rust not found`) — it was
+  reported as `python_dependency_resolution` (0.53). The boilerplate pattern is
+  dropped, so a build/metadata failure with no genuine resolution signal now
+  stays honest (`unknown`) instead. To keep recall on real conflicts, two
+  genuine pip signals were added: pip's actual Requires-Python wording
+  (`requires a different Python:`) and its no-distribution `(from versions: …)`
+  line; the three synthetic no-matching-distribution fixtures were updated to
+  include the real `(from versions: …)` output pip prints. Benchmark stays at
+  206/206 top-1 with all confidence floors met; the bundled dependency-failure
+  demo now reports 0.89 (three genuine resolution signals) instead of 0.95.
+  Regression covered in `tests/`.
+- `patchrail ci explain`/`classify` no longer hangs on large CI logs. The
+  `github_actions_workflow` rule paired two unanchored lookaheads
+  (`(?=[\s\S]*.github/workflows/…)(?=[\s\S]*Invalid workflow file…)`); under
+  `re.search` that compound is retried at every start position, so a log that
+  mentions `.github/workflows/*.yml` (every `actions/checkout` step does) but not
+  a workflow-error phrase drove the matcher into O(n²) backtracking and pegged a
+  core at 100% for minutes. Dogfooded against a real `cli/cli` Go CI run
+  (~200 KB) that never returned. The lookahead is now anchored with `\A` so it is
+  evaluated once, in linear time; the "workflow path AND error phrase present"
+  signal is unchanged. Regression covered in `tests/`.
+- Rust CI failures no longer misclassify as `node_dependency_install`,
+  `dotnet_build_failure`, or `java_build_failure` because of generic boilerplate.
+  The `Swatinem/rust-cache` action prints `Lockfiles considered:` (which matched
+  the old bare `lockfile` node signal) and cargo prints `build failed, waiting
+  for other jobs to finish` (which matched the case-insensitive `Build FAILED` /
+  `BUILD FAILED` banners). The node lockfile signal now requires a whole-word
+  `lockfile`, and the .NET/Gradle banners are matched case-sensitively so they
+  fire only on the tool's actual `Build FAILED` / `BUILD FAILED` output. A real
+  `tokio-rs/tokio` rustdoc failure (`error[E0433]`) now classifies as
+  `rust_test_failure`. Regression covered in `tests/`.
+- Sharper reproduce commands for three failure classes surfaced by `patchrail ci
+  classes` / `ci explain`. `node_script_missing` no longer suggests `npm run
+  build` (which just re-triggers the "missing script" error) and instead runs
+  `npm run` to list the scripts `package.json` actually defines, so you can
+  compare against the one your workflow calls. `security_scan_failure` names the
+  concrete scanners to rerun locally (`npm audit`, `pip-audit`, `cargo audit`,
+  `trivy fs .`, `bandit -r .`, `semgrep --config auto`) instead of the generic
+  "rerun the failing security scan locally". `github_actions_workflow` points at
+  `actionlint .github/workflows/`, which validates workflow syntax and action
+  refs locally, rather than only printing the YAML back with `gh workflow view`.
+- Real GitHub Actions logs no longer misclassify as `git_checkout_failure` when
+  checkout actually succeeded. The rule dropped three boilerplate signals that
+  appear in almost every Actions log regardless of outcome — the `actions/checkout`
+  setup step, the `git submodule foreach` post-job cleanup line, and a bare
+  `git-lfs` mention — keeping only genuine checkout/clone/submodule/LFS *failure*
+  markers (`fatal: ...`, `Failed to fetch submodule`, `smudge filter lfs failed`,
+  `error downloading object`, …). Dogfooded against a real `pallets/flask` CI run
+  whose pytest jobs failed on a conftest `SyntaxError` but were reported as a git
+  checkout problem.
+- `python_test_failure` now also recognizes pytest collection failures
+  (`ImportError while loading conftest ...`, `N errors during collection`), so a
+  broken `conftest.py` or import-time error surfaces as a test failure with the
+  `python -m pytest -q` reproduce line instead of falling through to a weaker or
+  wrong class.
+- `patchrail ci explain` and `ci classify` now fail clearly on empty or
+  whitespace-only input (from `--log` or stdin) instead of silently reporting
+  `failure_class: unknown` with confidence `0.15` and exit code `0`. They print
+  `log input is empty` to stderr, exit with code `2`, and write nothing to
+  `--out`, so a bad shell redirect is no longer mistaken for an unclassifiable
+  log. Closes #151.
+- Added `node_script_missing` to the published `ci-result` schema enum; the
+  classifier could already emit it, so a valid classification previously failed
+  schema validation for downstream consumers. A new test guards that every rule
+  class is declared in the schema enum.
+
+## 0.2.0 - 2026-07-07
+
+### Removed
+
+- Removed the commercial `Guide:` link that `ci explain` appended to text and
+  Markdown reports, and the matching guide URL outputs from the GitHub Action.
+  Reports now end after the classification; per-class remediation write-ups
+  live in-repo under `docs/fix/`.
+- Removed commercial product links and campaign-tagged URLs from the README,
+  docs, and the PyPI project URL list.
+- Removed the distribution and web-metrics tooling (`ci share-links` and the
+  web metrics commands and store). PatchRail no longer ships link-tracking or
+  distribution helpers.
+
+### Changed
+
+- `funded-issues` is now explicitly labeled experimental. Discovery commands
+  default to safe-only filtering, and risky entries require an explicit
+  `--include-risky` flag.
+- Rewrote the README around the open-source CI triage workflow: quickstart
+  with real classifier output, honest feature table, local-first safety
+  section, and the fixture contribution path.
+
+### Added
+
+- Added `node_script_missing` CI classification so npm/pnpm/yarn jobs that
+  call a missing package script are separated from dependency-install failures
+  and routed to a workflow/script repair path.
+- Added a permanent source-level blocklist to the funded-issues tracker:
+  owners manually verified as fake-bounty sources are dropped at the
+  `merge_into_store` choke point (counted as `blocked` in the merge summary)
+  and `purge_blocklisted_entries` removes any legacy entries; `track` runs the
+  purge on every merge so existing stores self-heal.
+- Added `funded-issues import-algora-board`, an offline parser for a locally
+  saved Algora organization bounty-board page. It extracts the funder-stated
+  USD amount, GitHub issue reference, posting age, and declared claim count
+  per bounty, and can merge the scored records into a tracker store. No
+  network access is performed.
+- Added read-only competition and payout-vs-effort scoring signals plus the
+  `funded-issues competition` and `funded-issues payout-effort` batch
+  commands, all derived from public metadata observations with no claims,
+  comments, or maintainer contact.
+- Added an offline owner-level `source_noise` heuristic and
+  `funded-issues apply-recheck`, a local-file-only command that transitions
+  tracker entries to closed / stale / active from recheck observations.
+- Added .NET/NuGet/C# and xUnit fixture coverage for `dotnet restore`,
+  `dotnet build`, and `dotnet test` failure modes, growing the public CI
+  fixture zoo to 153 cases.
+
+## 0.1.1 - 2026-06-12
+
+- `ci explain` now ends text and Markdown reports with a `Guide:` link to the
+  matching getpatchrail.com `/fix` remediation page; unknown or unpublished
+  failure classes fall back to the `/fix` index without a network call.
+- Added `funded-issues fresh`, a local read-only radar over the tracker store
+  that surfaces recently posted or recently labeled funded issues for fast
+  solver-side triage.
+- Added `pre_commit_hook_failure` CI classification so pre-commit hook output is
+  recognized directly while the CLI still avoids linking to a missing `/fix`
+  page until that guide exists.
+
+## 0.1.0 - 2026-06-02
+
+- Initial public CI Janitor snapshot.
+- Added `patchrail ci explain` and `patchrail ci classify`.
+- Added local Markdown, JSON, and text reports.
+- Added Apache-2.0 license and safety/ethics documentation.
+- Added fixture-backed tests, local benchmark command, and GitHub Actions CI.
+- Expanded the initial CI fixture zoo to 101 sanitized synthetic examples across
+  Python, Node, TypeScript, Go, Rust, and GitHub Actions failure modes.
+- Added a read-only GitHub Actions triage artifact workflow.
+- Added the experimental local Agent Control Plane queue with SQLite-backed
+  work items, approval states, audit export, CI result import, and proposal
+  records.
+- Added the experimental read-only `funded-issues` CLI over local metadata,
+  with safe-only filtering and explicit anti-abuse blocked actions.
+- Added permission-only adopter reporting and a public metrics tracker for
+  pilot outcomes, adoption signals, and open-source program evidence gaps.
+- Added release-prep evidence docs, package smoke checks, and manual publish
+  gates. Release tags, PyPI publishing, GitHub Releases, and public
+  announcements remain maintainer actions.

{patchrail-0.2.0 → patchrail-0.3.0}/CONTRIBUTING.md

@@ -22,7 +22,8 @@ patchrail redact --log failed-ci.log > failed-ci.redacted.log
 
 3. Review `failed-ci.redacted.log` manually and remove anything PatchRail should
    not publish: secrets, emails, private repo names, user names, customer names,
-   local home paths, and private URLs.
+   local home paths, and private URLs. See `docs/redaction.md` for exactly
+   which categories `patchrail redact` covers and which it doesn't.
 4. Reduce the log to the shortest excerpt that still shows the root cause.
 5. Add the fixture and expected metadata under `examples/ci-triage/`.
 6. Run the fixture hygiene gate and benchmark:
@@ -38,6 +39,10 @@ patchrail ci benchmark examples/ci-triage --format json
 If a real log cannot be safely redacted, create a minimal synthetic fixture that
 preserves the error pattern without preserving private identifiers.
 
+To catch a forgotten secret or a malformed fixture before it reaches a pull
+request, see `docs/pre-commit-example.md` for an optional pre-commit hook
+that runs `patchrail ci fixture-check` and `patchrail redact` automatically.
+
 ## Adding a CI fixture
 
 1. Copy the smallest failing log excerpt that still shows the root cause.

{patchrail-0.2.0 → patchrail-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: patchrail
-Version: 0.2.0
+Version: 0.3.0
 Summary: Local-first maintainer automation for open-source CI triage
 Project-URL: Homepage, https://github.com/patchrail/patchrail
 Project-URL: Documentation, https://github.com/patchrail/patchrail/tree/main/docs
@@ -49,11 +49,13 @@ entirely on your machine.
 
 ## Why maintainers use it
 
-- **33 failure classes** backed by real log signatures — dependency
+- **40 failure classes** backed by real log signatures — dependency
   resolution, flaky network, OOM-killed runners, Docker builds, lint,
-  type checks, and test failures across Python, Node, TypeScript, Go, Rust,
-  Java, .NET, Ruby, PHP, and C++.
-- **153 sanitized CI log fixtures** keep the classifier honest: every rule is
+  type checks, docs-site builds, and test failures across Python, Node,
+  TypeScript, Go, Rust, Java, .NET, Ruby, PHP, C++, and Swift/Xcode. Run
+  `patchrail ci classes` to list them all (add `--format json` to check
+  coverage from a script).
+- **169 sanitized CI log fixtures** keep the classifier honest: every rule is
   benchmarked against the public fixture zoo in `examples/ci-triage/` on every
   test run.
 - **23 secret-redaction patterns** (GitHub/GitLab/npm/PyPI/AWS tokens, private
@@ -91,7 +93,7 @@ Real output:
 # PatchRail CI Report
 
 - Root cause: `python_dependency_resolution`
-- Confidence: `0.95`
+- Confidence: `0.89`
 - Subsystem: Python dependency installation
 - Reproduce: `python -m pip install -r requirements.txt`
 - Suggested action: Pin or relax the conflicting dependency range, then rerun the same install command and the affected tests.
@@ -99,8 +101,8 @@ Real output:
 ## Evidence signals
 
 - `Could not find a version that satisfies the requirement`
+- `Cannot install .*because these package versions have conflicting dependencies`
 - `ResolutionImpossible`
-- `python -m pip install`
 ```
 
 It also reads from stdin, so you can pipe a log straight in:
@@ -129,14 +131,17 @@ leaves the job:
     log-path: test.log
 ```
 
-See [examples/ci-triage-action](examples/ci-triage-action/README.md) for the
-report artifact shape.
+The `@v1` drop-in exposes `failure-class`, `confidence`, and `guide-url`, plus a
+run annotation and job summary. See
+[docs/using-the-action.md](docs/using-the-action.md) for its full inputs and
+outputs, or [examples/ci-triage-action](examples/ci-triage-action/README.md) for
+the artifact shapes of both `@v1` and the richer in-repo composite.
 
 ## Features
 
 | Feature | Status | Notes |
 | --- | --- | --- |
-| CI failure triage (`ci explain`, `ci classify`) | Beta | 33 failure classes for GitHub Actions-style logs and common toolchains |
+| CI failure triage (`ci explain`, `ci classify`, `ci classes`) | Beta | 40 failure classes for GitHub Actions-style logs and common toolchains |
 | Secret redaction (`redact`, `ci explain --redact`) | Beta | 23 patterns for tokens, keys, emails, and home paths |
 | Reports | Beta | Markdown, JSON, and plain text |
 | Fixture benchmark (`ci benchmark`) | Beta | Scores the classifier against all 153 public fixtures |
@@ -179,9 +184,11 @@ Details in [docs/roadmap.md](docs/roadmap.md).
 ## Documentation
 
 - [Quickstart](docs/quickstart.md)
+- [jq cookbook for the JSON classifier output](docs/json-cookbook.md)
 - [Fix guides per failure class](docs/fix/README.md)
 - [CI Failure Zoo](docs/ci-failure-zoo.md)
 - [GitHub Actions CI triage](docs/github-action.md)
+- [Using the action in your own repository](docs/using-the-action.md)
 - [Agent Control Plane](docs/agent-control-plane.md)
 - [API reference](docs/api-reference.md)
 - [Threat model](docs/threat-model.md)

{patchrail-0.2.0 → patchrail-0.3.0}/README.md

@@ -18,11 +18,13 @@ entirely on your machine.
 
 ## Why maintainers use it
 
-- **33 failure classes** backed by real log signatures — dependency
+- **40 failure classes** backed by real log signatures — dependency
   resolution, flaky network, OOM-killed runners, Docker builds, lint,
-  type checks, and test failures across Python, Node, TypeScript, Go, Rust,
-  Java, .NET, Ruby, PHP, and C++.
-- **153 sanitized CI log fixtures** keep the classifier honest: every rule is
+  type checks, docs-site builds, and test failures across Python, Node,
+  TypeScript, Go, Rust, Java, .NET, Ruby, PHP, C++, and Swift/Xcode. Run
+  `patchrail ci classes` to list them all (add `--format json` to check
+  coverage from a script).
+- **169 sanitized CI log fixtures** keep the classifier honest: every rule is
   benchmarked against the public fixture zoo in `examples/ci-triage/` on every
   test run.
 - **23 secret-redaction patterns** (GitHub/GitLab/npm/PyPI/AWS tokens, private
@@ -60,7 +62,7 @@ Real output:
 # PatchRail CI Report
 
 - Root cause: `python_dependency_resolution`
-- Confidence: `0.95`
+- Confidence: `0.89`
 - Subsystem: Python dependency installation
 - Reproduce: `python -m pip install -r requirements.txt`
 - Suggested action: Pin or relax the conflicting dependency range, then rerun the same install command and the affected tests.
@@ -68,8 +70,8 @@ Real output:
 ## Evidence signals
 
 - `Could not find a version that satisfies the requirement`
+- `Cannot install .*because these package versions have conflicting dependencies`
 - `ResolutionImpossible`
-- `python -m pip install`
 ```
 
 It also reads from stdin, so you can pipe a log straight in:
@@ -98,14 +100,17 @@ leaves the job:
     log-path: test.log
 ```
 
-See [examples/ci-triage-action](examples/ci-triage-action/README.md) for the
-report artifact shape.
+The `@v1` drop-in exposes `failure-class`, `confidence`, and `guide-url`, plus a
+run annotation and job summary. See
+[docs/using-the-action.md](docs/using-the-action.md) for its full inputs and
+outputs, or [examples/ci-triage-action](examples/ci-triage-action/README.md) for
+the artifact shapes of both `@v1` and the richer in-repo composite.
 
 ## Features
 
 | Feature | Status | Notes |
 | --- | --- | --- |
-| CI failure triage (`ci explain`, `ci classify`) | Beta | 33 failure classes for GitHub Actions-style logs and common toolchains |
+| CI failure triage (`ci explain`, `ci classify`, `ci classes`) | Beta | 40 failure classes for GitHub Actions-style logs and common toolchains |
 | Secret redaction (`redact`, `ci explain --redact`) | Beta | 23 patterns for tokens, keys, emails, and home paths |
 | Reports | Beta | Markdown, JSON, and plain text |
 | Fixture benchmark (`ci benchmark`) | Beta | Scores the classifier against all 153 public fixtures |
@@ -148,9 +153,11 @@ Details in [docs/roadmap.md](docs/roadmap.md).
 ## Documentation
 
 - [Quickstart](docs/quickstart.md)
+- [jq cookbook for the JSON classifier output](docs/json-cookbook.md)
 - [Fix guides per failure class](docs/fix/README.md)
 - [CI Failure Zoo](docs/ci-failure-zoo.md)
 - [GitHub Actions CI triage](docs/github-action.md)
+- [Using the action in your own repository](docs/using-the-action.md)
 - [Agent Control Plane](docs/agent-control-plane.md)
 - [API reference](docs/api-reference.md)
 - [Threat model](docs/threat-model.md)

patchrail-0.3.0/examples/ci-triage/appveyor-dotnet-test-xunit.log

@@ -0,0 +1,10 @@
+> dotnet test .\src\Billing.Tests\Billing.Tests.csproj
+Starting test execution, please wait...
+[xUnit.net 00:00:01.24]     Billing.Tests.InvoiceCalculatorTests.AppliesTaxRate_ForRegion [FAIL]
+[xUnit.net 00:00:01.24]       Assert.Equal() Failure
+[xUnit.net 00:00:01.24]       Expected: 108.50m
+[xUnit.net 00:00:01.24]       Actual:   108.00m
+  Failed Billing.Tests.InvoiceCalculatorTests.AppliesTaxRate_ForRegion [12 ms]
+
+Failed!  - Failed:     1, Passed:    46, Skipped:     0, Total:    47
+Command exited with code 1

patchrail-0.3.0/examples/ci-triage/azure-pipelines-dotnet-test.log

@@ -0,0 +1,18 @@
+##[section]Starting: dotnet test
+==============================================================================
+Task         : .NET Core
+Description  : Build, test, package, or publish a dotnet application
+==============================================================================
+##[command]dotnet test ./tests/Billing.Tests.csproj --logger trx
+Starting test execution, please wait...
+
+  X Billing.Tests.InvoiceCalculatorTests.AppliesDiscountAboveThreshold [12 ms]
+  Error Message:
+   Xunit.Sdk.EqualException
+   Assert.Equal() Failure
+   Expected: 90.00m
+   Actual:   100.00m
+
+Failed!  - Failed:     1, Passed:    47, Skipped:     0, Total:    48
+##[error]Process completed with exit code 1.
+##[section]Finishing: dotnet test

patchrail-0.3.0/examples/ci-triage/bitbucket-pipelines-composer-platform.log

@@ -0,0 +1,10 @@
++ composer install --no-dev --prefer-dist
+Loading composer repositories with package information
+Updating dependencies
+Your requirements could not be resolved to an installable set of packages.
+
+  Problem 1
+    - Root composer.json requires php >=8.2 but your php version (8.1.27) does not satisfy that requirement.
+    - vendor/example/pdf-toolkit v3.0.1 requires php >=8.2 -> your php version (8.1.27) does not satisfy that requirement.
+
+Build failed with exit code 2

patchrail-0.3.0/examples/ci-triage/bitbucket-pipelines-npm-eresolve.log

@@ -0,0 +1,18 @@
++ npm install
+npm ERR! code ERESOLVE
+npm ERR! ERESOLVE unable to resolve dependency tree
+npm ERR!
+npm ERR! While resolving: checkout-service@2.1.0
+npm ERR! Found: react@18.3.1
+npm ERR! node_modules/react
+npm ERR!   react@"^18.3.1" from the root project
+npm ERR!
+npm ERR! Could not resolve dependency:
+npm ERR! peer react@"^17.0.0" from react-legacy-widgets@4.2.0
+npm ERR! node_modules/react-legacy-widgets
+npm ERR!   react-legacy-widgets@"^4.2.0" from the root project
+npm ERR!
+npm ERR! Fix the upstream dependency conflict, or retry
+npm ERR! this command with --force or --legacy-peer-deps
+npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2026-07-08T09_12_00_000Z-debug-0.log
+Build failed with exit code 1.

patchrail-0.3.0/examples/ci-triage/bitbucket-pipelines-vue-tsc-typecheck.log

@@ -0,0 +1,14 @@
++ vue-tsc --noEmit -p tsconfig.json --composite false
+src/components/OrderSummary.vue:28:11 - error TS2322: Type 'number | undefined' is not assignable to type 'number'.
+
+28   <TotalLabel :amount="order.total" />
+             ~~~~~~
+
+  src/types/order.ts:9:3
+    9   total: number;
+        ~~~~~
+    The expected type comes from property 'total' which is declared here on type 'Order'.
+
+Found 1 error in src/components/OrderSummary.vue:28
+
+Build failed with exit code 2

patchrail-0.3.0/examples/ci-triage/buildkite-docker-build.log

@@ -0,0 +1,8 @@
+~~~ Running commands
+$ docker build -t app:ci .
+[+] Building 4.2s (8/12)
+#8 [5/9] COPY app/config/production.yaml /app/config/production.yaml
+failed to solve: failed to compute cache key: "/app/config/production.yaml": not found
+no such file or directory
+^^^ +++
+user command error: exited with status 1

patchrail-0.3.0/examples/ci-triage/buildkite-pnpm-frozen-lockfile.log

@@ -0,0 +1,11 @@
+~~~ Running commands
+$ pnpm install --frozen-lockfile
+Lockfile is up to date, resolution step is skipped
+Fetching dependencies
+
+ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with dashboard-ui/package.json
+
+  Failure reason:
+  specifiers in the lockfile ({"date-fns":"^2.30.0"}) don't match specs in package.json ({"date-fns":"^3.6.0"})
+
+user command error: exited with status 1

patchrail-0.3.0/examples/ci-triage/cargo-test-panic-failure.log

@@ -0,0 +1,11 @@
+Run cargo test
+running 12 tests
+thread 'store::tests::rejects_negative_balance' panicked at crates/store/src/lib.rs:58:9:
+assertion failed: `(left == right)`
+  left: `-5`,
+ right: `0`
+test store::tests::rejects_negative_balance ... FAILED
+
+test result: FAILED. 11 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out
+
+error: test failed, to rerun pass `-p store --lib`

patchrail-0.3.0/examples/ci-triage/circleci-bundler-native-extension.log

@@ -0,0 +1,15 @@
+#!/bin/bash -eo pipefail
+bundle install --jobs=4 --retry=3
+Fetching gem metadata from https://rubygems.org/...
+Installing nokogiri 1.16.5 with native extensions
+Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
+
+    current directory: /builds/project/vendor/bundle/ruby/3.2.0/gems/nokogiri-1.16.5/ext/nokogiri
+/usr/bin/ruby3.2 extconf.rb
+checking if the C compiler accepts ... *** extconf.rb failed ***
+Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers.
+Check the mkmf.log file for more details.
+
+An error occurred while installing nokogiri (1.16.5), and Bundler cannot continue.
+
+Exited with code exit status 1

patchrail-0.3.0/examples/ci-triage/circleci-checkout-lfs-failure.expected.json

@@ -0,0 +1,4 @@
+{
+  "failure_class": "git_checkout_failure",
+  "minimum_confidence": 0.7
+}

patchrail-0.3.0/examples/ci-triage/circleci-checkout-lfs-failure.log

@@ -0,0 +1,9 @@
+#!/bin/bash -eo pipefail
+Checkout code
+Cloning git repository
+Cloning into 'project'...
+Downloading assets/demo-render.mov (82 MB)
+Error downloading object: assets/demo-render.mov (a1b2c3d): Smudge error: Error downloading assets/demo-render.mov (a1b2c3d4e5f67890): smudge filter lfs failed
+error downloading object
+
+Exited with code exit status 1

patchrail-0.3.0/examples/ci-triage/circleci-oom-exit-137.expected.json

@@ -0,0 +1,4 @@
+{
+  "failure_class": "runner_resource_exhaustion",
+  "minimum_confidence": 0.7
+}

patchrail-0.3.0/examples/ci-triage/circleci-oom-exit-137.log

@@ -0,0 +1,12 @@
+#!/bin/bash -eo pipefail
+yarn build
+$ yarn build
+yarn run v1.22.19
+$ webpack --mode production
+<--- Last few GCs --->
+
+FATAL ERROR: JavaScript heap out of memory
+Out of memory: Killed process 412 (node) total-vm:5231212kB
+
+Exited with code exit status 137
+CircleCI received exit code 137

patchrail-0.3.0/examples/ci-triage/cirrus-ci-cargo-test-panic.log

@@ -0,0 +1,18 @@
+$ cargo test --workspace
+running 18 tests
+test scheduler::tests::retries_backoff_capped ... FAILED
+
+failures:
+
+---- scheduler::tests::retries_backoff_capped stdout ----
+thread 'scheduler::tests::retries_backoff_capped' panicked at crates/scheduler/src/lib.rs:73:9:
+assertion `left == right` failed
+  left: 32
+ right: 30
+
+failures:
+    scheduler::tests::retries_backoff_capped
+
+test result: FAILED. 17 passed; 1 failed; 0 ignored; 0 measured
+error: test failed, to rerun pass `-p scheduler --lib`
+Cirrus CI task failed with exit code 101

patchrail-0.3.0/examples/ci-triage/cloudbuild-golangci-lint-failure.expected.json

@@ -0,0 +1,4 @@
+{
+  "failure_class": "go_lint",
+  "minimum_confidence": 0.7
+}

patchrail-0.3.0/examples/ci-triage/cloudbuild-golangci-lint-failure.log

@@ -0,0 +1,6 @@
+Step #2 - "lint": + golangci-lint run ./...
+Step #2 - "lint": internal/pricing/discount.go:58:2: ineffectual assignment to err (ineffassign)
+Step #2 - "lint": internal/pricing/discount.go:71:14: S1021: should merge variable declaration with assignment (gosimple)
+Step #2 - "lint": 2 issues found
+Finished Step #2 - "lint"
+ERROR: build step 2 "golangci/golangci-lint" failed: exit status 1

patchrail-0.3.0/examples/ci-triage/codebuild-jest-test-failure.expected.json

@@ -0,0 +1,4 @@
+{
+  "failure_class": "node_test_failure",
+  "minimum_confidence": 0.7
+}

patchrail-0.3.0/examples/ci-triage/codebuild-jest-test-failure.log

@@ -0,0 +1,19 @@
+[Container] Running command npm test
+
+> checkout-api@1.4.0 test
+> jest --ci
+
+FAIL src/handlers/refund.test.ts
+  refund handler
+    ✕ rejects refunds above the remaining balance (14 ms)
+
+  ● refund handler > rejects refunds above the remaining balance
+
+    expect(received).toBe(expected)
+
+    Expected: 400
+    Received: 200
+
+Tests:       1 failed, 22 passed, 23 total
+Test Suites: 1 failed, 6 passed, 7 total
+[Container] Command did not exit successfully npm test exit status 1

patchrail-0.3.0/examples/ci-triage/codefresh-trivy-critical.expected.json

@@ -0,0 +1,4 @@
+{
+  "failure_class": "security_scan_failure",
+  "minimum_confidence": 0.7
+}

patchrail-0.3.0/examples/ci-triage/codefresh-trivy-critical.log

@@ -0,0 +1,15 @@
+Step: Scan image
+$ trivy image --exit-code 1 --severity CRITICAL registry.example.com/api-gateway:sha-9f31c02
+
+api-gateway:sha-9f31c02 (alpine 3.18.4)
+=======================================
+Total: 2 (CRITICAL: 2)
+
++-------------+------------------+----------+-------------------+---------------+
+|   LIBRARY   | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |
++-------------+------------------+----------+-------------------+---------------+
+| openssl     | CVE-2024-0727    | CRITICAL | 3.1.4-r0           | 3.1.4-r5      |
+| libcrypto3  | CVE-2024-0727    | CRITICAL | 3.1.4-r0           | 3.1.4-r5      |
++-------------+------------------+----------+-------------------+---------------+
+
+Codefresh step failed: exit code 1