@htekdev/actions-debugger 1.0.25 → 1.0.27

package/errors/runner-environment/powershell-76-dotnet10-httpclient-breaking-changes.yml

@@ -0,0 +1,109 @@
+id: runner-environment-079
+title: "PowerShell 7.6 on Runners Ships .NET 10 Runtime — HttpWebRequest and WebClient Throw NotSupportedException"
+category: runner-environment
+severity: error
+tags:
+  - powershell
+  - powershell-76
+  - dotnet-10
+  - dotnet-8
+  - runner-images
+  - breaking-change
+  - httpclient
+  - webclient
+patterns:
+  - regex: 'NotSupportedException.*HttpWebRequest|WebClient.*NotSupportedException'
+    flags: "i"
+  - regex: 'ServicePointManager.*SecurityProtocol.*not supported|The method or operation is not implemented'
+    flags: "i"
+  - regex: 'MissingMethodException.*ServicePointManager|System\.Net\.WebException.*NotSupported'
+    flags: "i"
+  - regex: 'WildcardPattern\.Escape.*backtick|Join-Path.*ChildPath.*string\[\]'
+    flags: "i"
+error_messages:
+  - "System.NotSupportedException: WebClient has been removed from .NET"
+  - "System.NotSupportedException: HttpWebRequest is not supported on this platform"
+  - "System.MissingMethodException: Method not found: 'Void System.Net.ServicePointManager.set_SecurityProtocol'"
+root_cause: |
+  PowerShell 7.4 was built on .NET 8. PowerShell 7.6 is built on .NET 10.
+  Beginning June 8-15, 2026, all GitHub-hosted runner images upgraded from PS 7.4
+  to PS 7.6 LTS (runner-images#14150). This introduces several .NET 10 breaking changes:
+
+  1. HttpWebRequest and WebClient have been fully removed in .NET 10.
+     Any PowerShell script that uses New-Object System.Net.WebClient or
+     [System.Net.HttpWebRequest]::Create() now throws NotSupportedException.
+     Both classes were deprecated in .NET 5 and are gone in .NET 10.
+
+  2. ServicePointManager.SecurityProtocol setter is not supported in .NET 10.
+     Workflows that manually set TLS protocol versions with
+     [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
+     now throw MissingMethodException. .NET 10 negotiates TLS automatically.
+
+  3. WildcardPattern.Escape now correctly escapes lone backtick characters (PS #25211).
+     Scripts that relied on the previous (incorrect) unescaped behavior may match
+     different patterns than expected.
+
+  4. Join-Path -ChildPath parameter changed from string to string[]. Code that relied
+     on positional argument behavior for this parameter may bind differently.
+
+  This is distinct from the ThreadJob module rename (runner-environment-075 entry).
+  These are .NET runtime-level breaking changes, not module renames.
+fix: |
+  Replace HttpWebRequest / WebClient with Invoke-RestMethod or Invoke-WebRequest,
+  which are the PowerShell-native HTTP clients backed by HttpClient (supported in all
+  .NET versions). Remove ServicePointManager.SecurityProtocol assignments entirely;
+  .NET 10 negotiates TLS 1.2/1.3 automatically and no longer accepts manual overrides.
+fix_code:
+  - language: yaml
+    label: "Replace WebClient (removed in .NET 10) with Invoke-WebRequest"
+    code: |
+      steps:
+        - name: Download file
+          shell: pwsh
+          run: |
+            # BEFORE (.NET 10 throws NotSupportedException):
+            # $wc = New-Object System.Net.WebClient
+            # $wc.DownloadFile($env:URL, $env:DEST)
+
+            # AFTER — use Invoke-WebRequest (works across .NET 6/8/10)
+            Invoke-WebRequest -Uri $env:ARTIFACT_URL -OutFile $env:DEST_PATH -UseBasicParsing
+          env:
+            ARTIFACT_URL: 'https://example.com/artifact.zip'
+            DEST_PATH: 'artifact.zip'
+  - language: yaml
+    label: "Remove ServicePointManager.SecurityProtocol (not needed in .NET 10)"
+    code: |
+      steps:
+        - name: Call API
+          shell: pwsh
+          run: |
+            # BEFORE (.NET 10 throws MissingMethodException):
+            # [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
+
+            # AFTER — .NET 10 negotiates TLS 1.3/1.2 automatically, no manual override needed
+            $response = Invoke-RestMethod -Uri 'https://api.example.com/data' -Method Get
+            $response | ConvertTo-Json
+  - language: yaml
+    label: "Check PowerShell version in workflow to detect the upgrade"
+    code: |
+      steps:
+        - name: Verify PowerShell version and .NET runtime
+          shell: pwsh
+          run: |
+            $PSVersionTable
+            [System.Environment]::Version
+prevention:
+  - "Audit all PowerShell scripts in workflows for WebClient and HttpWebRequest usage before the June 8-15 image rollout."
+  - "Replace New-Object System.Net.WebClient with Invoke-WebRequest or Invoke-RestMethod throughout."
+  - "Remove all [System.Net.ServicePointManager]::SecurityProtocol assignments — they are no-ops at best in .NET 10."
+  - "Test workflows locally with PowerShell 7.6 (winget install Microsoft.PowerShell) before the image rollout completes."
+  - "The ThreadJob module rename is a separate issue — see runner-environment-075 entry for that breaking change."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14150"
+    label: "runner-images#14150: PowerShell will be updated from 7.4 to 7.6 LTS on all runner images"
+  - url: "https://learn.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-76"
+    label: "Microsoft Docs: What's new in PowerShell 7.6"
+  - url: "https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-10/overview"
+    label: "Microsoft Docs: Breaking changes in .NET 10"
+  - url: "https://github.com/PowerShell/PowerShell/releases/tag/v7.6.0"
+    label: "PowerShell 7.6.0 Release Notes"

package/errors/runner-environment/ubuntu-24-04-chrome-148-webdriverio-hang.yml

@@ -0,0 +1,91 @@
+id: runner-environment-077
+title: "Chrome 148.0.7778.178 on Ubuntu 24.04 Causes WebdriverIO and Browser Tests to Hang"
+category: runner-environment
+severity: error
+tags:
+  - ubuntu-24.04
+  - chrome
+  - chromium
+  - webdriverio
+  - browser-testing
+  - regression
+  - selenium
+  - playwright
+patterns:
+  - regex: 'Failed to create session|chrome not reachable|connect ECONNREFUSED.*9515'
+    flags: "i"
+  - regex: 'ChromeDriver.*unable to receive message|WebDriver.*timed out'
+    flags: "i"
+  - regex: 'google-chrome.*148\.0\.7778\.17[89]|148\.0\.7778\.17[89]'
+    flags: "i"
+error_messages:
+  - "Error: Failed to create session."
+  - "Error: chrome not reachable"
+  - "Error: connect ECONNREFUSED 127.0.0.1:9515"
+  - "DevTools protocol message timeout"
+root_cause: |
+  Chrome 148.0.7778.178 was shipped in ubuntu-24.04 runner image 20260525.161.1
+  (May 25, 2026). This build introduced an upstream regression that causes WebdriverIO,
+  Selenium, and other CDP-based browser automation frameworks to hang indefinitely
+  when launching Chrome. The Chrome process starts but the DevTools Protocol endpoint
+  never becomes reachable, causing session creation to time out.
+
+  GitHub installs Chrome from the official stable channel on each image build and does
+  not pin versions. The previous image (20260518.149.1) shipped Chrome 148.0.7778.167
+  which was unaffected. GitHub confirmed they will not roll back the image and are
+  waiting for an upstream Google Chrome fix (tracked as Chromium issue #517079992).
+
+  WebdriverIO tests that previously ran reliably on GitHub-hosted ubuntu-24.04 runners
+  will hang silently or time out after this image version update. Switching to
+  ubuntu-22.04 does not guarantee relief as it also installs stable Chrome.
+fix: |
+  Pin Chrome to version 148.0.7778.167 (the last known-good stable build) using
+  browser-actions/setup-chrome, which installs from Chrome for Testing CDN — an
+  immutable, version-pinned registry that does not auto-update. Point WebdriverIO at
+  the pinned Chrome binary via environment variables rather than using system Chrome.
+fix_code:
+  - language: yaml
+    label: "Pin Chrome to last known-good build (runner-images#14169 workaround)"
+    code: |
+      jobs:
+        e2e:
+          runs-on: ubuntu-24.04
+          steps:
+            - uses: actions/checkout@v4
+
+            - name: Install pinned Chrome (workaround for runner-images#14169)
+              id: setup-chrome
+              uses: browser-actions/setup-chrome@v1
+              with:
+                chrome-version: '148.0.7778.167'
+                install-dependencies: true
+                install-chromedriver: true
+
+            - name: Run E2E tests with pinned Chrome
+              env:
+                CHROME_BIN: ${{ steps.setup-chrome.outputs.chrome-path }}
+                CHROMEWEBDRIVER: ${{ steps.setup-chrome.outputs.chromedriver-path }}
+              run: npx wdio run wdio.conf.js
+  - language: yaml
+    label: "WebdriverIO capability config pointing to pinned Chrome binary"
+    code: |
+      # wdio.conf.js — use CHROME_BIN from the setup-chrome step, not system Chrome
+      capabilities: [{
+        browserName: 'chrome',
+        'goog:chromeOptions': {
+          binary: process.env.CHROME_BIN,
+          args: ['--headless=new', '--no-sandbox', '--disable-dev-shm-usage'],
+        },
+      }]
+prevention:
+  - "Never rely on the system Chrome version in CI — pin via browser-actions/setup-chrome for reproducible builds."
+  - "Configure WebdriverIO to use CHROME_BIN environment variable instead of auto-detecting /usr/bin/google-chrome."
+  - "Subscribe to actions/runner-images#14169 to learn when a fixed Chrome stable is shipped."
+  - "Consider Playwright (brings its own browser binaries) as a long-term alternative to avoid runner image Chrome updates."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/14169"
+    label: "runner-images#14169: Ubuntu 24.04 image update causes WebdriverIO tests with updated Chrome to hang"
+  - url: "https://github.com/browser-actions/setup-chrome"
+    label: "browser-actions/setup-chrome: Install pinned Chrome for Testing builds"
+  - url: "https://googlechromelabs.github.io/chrome-for-testing/"
+    label: "Chrome for Testing: Immutable Chrome binaries by version (CDN)"

package/errors/runner-environment/ubuntu-24-04-kernel-read-ahead-kb-io-thrashing.yml

@@ -0,0 +1,94 @@
+id: runner-environment-076
+title: "Ubuntu 24.04 Kernel read_ahead_kb Regression Causes I/O Thrashing and Workflow Hangs"
+category: runner-environment
+severity: error
+tags:
+  - ubuntu-24.04
+  - kernel
+  - io-thrashing
+  - memory
+  - docker
+  - read-ahead
+  - performance
+patterns:
+  - regex: 'The hosted runner lost communication with the server'
+    flags: "i"
+  - regex: 'Free memory is lower than 5%|Currently used: 9[0-9]\.[0-9]+%'
+    flags: "i"
+  - regex: 'Out of memory, malloc failed|fatal: the remote end hung up unexpectedly'
+    flags: "i"
+error_messages:
+  - "The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error."
+  - "##[warning]Free memory is lower than 5%; Currently used: 95.55%"
+  - "fatal: Out of memory, malloc failed (tried to allocate 217 bytes)"
+  - "fatal: the remote end hung up unexpectedly"
+root_cause: |
+  Starting with kernel 6.14.0-1017-azure (shipped in ubuntu-24.04 image 20260224.36.1
+  and continuing with 6.17.0-1008-azure in 20260302.42.1 through current), the default
+  read_ahead_kb block device value was changed from 128 KB to 4096 KB. This causes
+  the Linux page cache to speculatively read 32x more data from disk for each I/O
+  operation, flooding available RAM with unused prefetched data.
+
+  The effect is severe for workloads with large files accessed non-sequentially
+  (many build systems, compilation), Docker-in-Docker setups, database integration
+  tests (Postgres, MySQL, Redis) under I/O load, and large repository operations.
+
+  The page cache exhaustion triggers OOM conditions, process starvation, and eventually
+  causes the Actions runner process to lose connectivity to the GitHub Actions broker,
+  manifesting as "The hosted runner lost communication with the server."
+
+  GitHub confirmed this is a kernel-level change they do not control and cannot roll
+  back. The fix must be applied in the workflow. Independently documented by the
+  RavenDB team for the same Azure kernel change.
+fix: |
+  Add a step at the beginning of the job to reset read_ahead_kb to 128 KB (the
+  safe pre-regression value). This must run before any I/O-intensive steps.
+  The step requires sudo access, which is available on all GitHub-hosted runners.
+fix_code:
+  - language: yaml
+    label: "Reset read_ahead_kb before I/O-intensive steps (kernel regression workaround)"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-24.04
+          steps:
+            - name: Reset block device read-ahead (kernel regression workaround for runner-images#13770)
+              run: |
+                for dev in /sys/block/sd*/queue/read_ahead_kb; do
+                  echo 128 | sudo tee "$dev" > /dev/null
+                done
+                echo "read_ahead_kb reset to 128 on all block devices"
+
+            - uses: actions/checkout@v4
+            - name: Build
+              run: make
+  - language: yaml
+    label: "Diagnose memory pressure before applying the workaround"
+    code: |
+      jobs:
+        build:
+          runs-on: ubuntu-24.04
+          steps:
+            - name: Show current read_ahead_kb and available memory
+              run: |
+                cat /sys/block/sda/queue/read_ahead_kb || true
+                free -h
+
+            - name: Reset read_ahead_kb to safe value
+              run: |
+                for dev in /sys/block/sd*/queue/read_ahead_kb; do
+                  echo 128 | sudo tee "$dev" > /dev/null
+                done
+                cat /sys/block/sda/queue/read_ahead_kb
+prevention:
+  - "Always reset read_ahead_kb to 128 on ubuntu-24.04 runners for workflows with Docker containers or database integration tests."
+  - "Use ubuntu-22.04 as a temporary mitigation — kernel 6.8.0 is unaffected by this regression."
+  - "Add memory diagnostics (free -h) before heavy build steps to catch exhaustion early."
+  - "Monitor actions/runner-images#13770 for a permanent kernel fix from Canonical and GitHub."
+docs:
+  - url: "https://github.com/actions/runner-images/issues/13770"
+    label: "runner-images#13770: ubuntu-latest builds hanging in 20260302.42.1 runner image (kernel regression)"
+  - url: "https://github.com/ravendb/ravendb/discussions/22410"
+    label: "RavenDB: Azure kernel read_ahead_kb change causing I/O thrashing"
+  - url: "https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners"
+    label: "GitHub Docs: GitHub-hosted runner hardware resources"

package/package.json

@@ -1,18 +1,19 @@
 {
   "name": "@htekdev/actions-debugger",
-  "version": "1.0.25",
-  "description": "65+ real GitHub Actions errors, queryable by agents. MCP server + Copilot skills + error database.",
+  "version": "1.0.27",
+  "description": "65+ real GitHub Actions errors, queryable by agents. CLI + MCP server + Copilot skills + error database.",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
-    "actions-debugger": "./dist/index.js"
+    "actions-debugger": "./dist/entry.js"
   },
   "exports": {
     ".": {
       "import": "./dist/index.js",
       "types": "./dist/index.d.ts"
-    }
+    },
+    "./mcp": "./dist/mcp.js"
   },
   "files": [
     "dist",
@@ -27,7 +28,9 @@
     "test:watch": "vitest",
     "lint": "tsc --noEmit",
     "validate-errors": "node --import tsx scripts/validate-errors.ts",
-    "start": "node dist/index.js",
+    "start": "node dist/mcp.js",
+    "start:mcp": "node dist/mcp.js",
+    "start:cli": "node dist/entry.js",
     "prepublishOnly": "npm run build"
   },
   "publishConfig": {
@@ -40,7 +43,8 @@
     "model-context-protocol",
     "copilot",
     "ci-cd",
-    "error-database"
+    "error-database",
+    "cli"
   ],
   "author": "Hector Flores <hector.flores@htek.dev> (https://htek.dev)",
   "license": "MIT",
@@ -54,6 +58,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.0",
+    "commander": "^15.0.0",
     "glob": "^11.0.0",
     "js-yaml": "^4.1.0"
   },