claude-code - 💡(How to fix) Fix [Bug] Unresolved issues marked as pre-existing instead of addressing regressions

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/magic/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n at sd_ (/$bunfs/root/src/entrypoints/cli.js:2751:2177)\n at WH8 (/$bunfs/root/src/entrypoints/cli.js:2751:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T10:52:31.641Z"},{"error":"AxiosError: Request failed with status code 404\n at CU (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12744)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T10:52:54.834Z"}]

TL;DR

The issue may be resolved by addressing the lock acquisition failure and the AxiosError with a 404 status code, potentially by checking file system permissions and ensuring the requested resource is available.

Guidance

• Investigate the lock acquisition failure by checking the file system permissions for /Users/magic/.local/share/claude/versions/2.1.114 to ensure the process has the necessary access rights.
• Verify that the resource requested by the Axios call is available and correctly referenced, as the 404 status code indicates it cannot be found.
• Consider checking for any multi-process scenarios that might be causing the lock acquisition failure, as hinted in the error message.
• Review the cli.js file, specifically lines 2751 and 110, for any potential issues related to lock acquisition and Axios requests.

Example

No specific code snippet can be provided without more context, but ensuring proper error handling for Axios requests, such as catching and logging errors, might help in debugging:

try {
  const response = await axios.get('requestedResourceUrl');
  // Handle response
} catch (error) {
  if (axios.isAxiosError(error)) {
    console.log('Axios error:', error.message);
  } else {
    console.log('Unexpected error:', error);
  }
}

Notes

The provided information does not specify the exact cause of the lock acquisition failure or the AxiosError, so these steps are speculative based on the error messages. Further investigation into the application's logic and environment is necessary for a definitive fix.

Recommendation

Apply workaround: Given the lack of a clear solution from the provided information, applying a workaround such as manually adjusting file system permissions or verifying the existence and accessibility of the requested resource might be the most immediate step towards resolving the issue.