Skip to content

fix(git): time out cached commands - #559

Open
SR0725 wants to merge 1 commit into
sirmalloc:mainfrom
SR0725:fix/git-cache-command-timeout
Open

fix(git): time out cached commands#559
SR0725 wants to merge 1 commit into
sirmalloc:mainfrom
SR0725:fix/git-cache-command-timeout

Conversation

@SR0725

@SR0725 SR0725 commented Aug 24, 2026

Copy link
Copy Markdown

What changed

Git widgets use the cached command runner in src/utils/git.ts. On a cache miss, that runner called Git without a timeout, so a blocked Git process could also block the status line indefinitely.

This applies the existing five-second command boundary used by the other Git runner. A timeout still follows the current failure path: the widget gets no Git value and the result is cached normally.

Validation

  • bun test src/utils/__tests__/git.test.ts (53 passed)
  • bun test (1,868 passed)
  • bun run lint
  • bun run build

The regression assertion verifies that every cached Git command receives the five-second timeout. The compatibility risk is limited to Git commands that take longer than five seconds; those now return no widget value instead of blocking the process.

Fixes #557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No timeout on the cached git exec, unlike every other CLI call site (2.2.22)

1 participant