[Bug] File system watcher fails with unhandled promise rejection in FSWatcher

Resolved 💬 3 comments Opened Dec 22, 2025 by GoosLab Closed Dec 26, 2025

Bug Description
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Unknown Error, TODO
at watch (unknown)
at new FSWatcher (node:fs:29:31)
at watch (node:fs:296:23)
at BC_ (/$bunfs/root/claude:392:6265)
at bMD (/$bunfs/root/claude:392:11479)
at _watchWithNodeFs (/$bunfs/root/claude:392:6746)
at _handleFile (/$bunfs/root/claude:392:7489)
at _addToNodeFs (/$bunfs/root/claude:392:10516)
at processTicksAndRejections (native:7:39)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Unknown Error, TODO
at watch (unknown)
at new FSWatcher (node:fs:29:31)
at watch (node:fs:296:23)
at BC_ (/$bunfs/root/claude:392:6265)

Environment Info

  • Platform: darwin
  • Terminal: cursor
  • Version: 2.0.75
  • Feedback ID: 14c9ae9e-26bc-442f-a044-21988f1cd20d

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/goos/.local/share/claude/versions/2.0.75 (expected in multi-process scenarios)\n    at XZR (/$bunfs/root/claude:2430:2165)\n    at bUA (/$bunfs/root/claude:2430:1885)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-22T17:07:37.090Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗