Verification Results for #5057 — Update error handling with CLI and MCP calls

GitLens version: 2026.3.2705 (pre-release)
Environment: Windows 11, VS Code, workspace Testing_gl_rc17.12

✅ 1. Invalid JSON in IPC request body

Method: Sent HTTP requests with malformed JSON bodies directly to the IPC server via Node.js HTTP client (port discovered from the discovery file in %TEMP%/gitkraken/gitlens/).

Test cases:

Body: this is not valid json{{{ → HTTP 400 Invalid JSON ✅
Body: {"command": "git status" (truncated) → HTTP 400 Invalid JSON ✅
Body: empty → HTTP 200 (no regression) ✅
Body: valid JSON → HTTP 200 (no regression) ✅

✅ 2. Protection against multiple IPC servers running simultaneously

Method: Repeatedly toggled gitlens.gitkraken.cli.integration.enabled in settings.json (OFF→ON×2 cycles) to trigger start() multiple times. Scanned all discovery files and checked active ports via http.request after each toggle.

Results:

Each new start() call properly stopped the previous server (stop() called first)
After 2 full cycles: exactly 1 active server per workspace at all times
Old ports (56479, 63327) were dead, replaced by new ones — no leaked servers

✅ 3. IPC server creation failure — logging and graceful exit

Method: Injected throw new Error("[TEST] IPC server creation failed") at the beginning of the createIpcServer function (sH()) in the installed extension bundle (dist/gitlens.js). Reloaded VS Code window, then inspected GitLens.log.

Results:

Extension did not crash

Log entry confirmed in Output Channel / GitLens.log:

2026-03-27 16:03:20.237 [error] Error: [TEST] Simulated IPC server creation failure
  Failed to start CLI integration IPC server

IPC server did not start → no active discovery file created
MCP server was unavailable (graceful, no exception propagated)

✅ 4. Telemetry events `cli/ipc/failed` and `cli/discoveryFile/failed`

Method:

Redirected the OTLP endpoint in dist/telemetry.js from https://otel.gitkraken.com/v1/traces to a local mock HTTP server (http://127.0.0.1:14318), disabled gzip compression for readable JSON.
Test A — injected throw into createIpcServer (sH()), reloaded VS Code → captured cli/ipc/failed.
Test B — restored sH(), injected throw into createDiscoveryFile (s1()), reloaded VS Code → captured cli/discoveryFile/failed.
Restored all original files after testing.

Captured events:

cli/ipc/failed:

EVENT: cli/ipc/failed
  error.message: [TEST] IPC server creation failed
  global.prerelease: true

cli/discoveryFile/failed:

EVENT: cli/discoveryFile/failed
  error.message: [TEST] Discovery file creation failed
  global.prerelease: true

MCP server appeared in stopped (not crashed) state during cli/discoveryFile/failed test — IPC server started correctly, only discovery file was missing.

✅ 5. Regression — normal scenario

Method: After restoring all original files and full VS Code reload — tested all MCP tools via direct IPC requests using the active discovery file.

Results (GitLens 2026.3.2705, IPC port 50409):

Tool	HTTP	Result
`mcp/launchpad/list`	200	Returned items list
`mcp/launchpad/item`	200	Returned item details
`mcp/wip/compose/open`	200	UI action triggered
`mcp/pr/review/start`	200	Endpoint responds
`mcp/issue/start` (nikolay-1986/gk-gl-test-github#2)	200	Branch + worktree created

Update error handling with CLI and MCP calls #5057

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions