gemini-cli - 💡(How to fix) Fix [Bug] CLI crashes with ENAMETOOLONG when pasting long strings into prompt [3 comments, 2 participants]

CRITICAL: Unhandled Promise Rejection! Reason: Error: ENAMETOOLONG: name too long, lstat '/Users/huyitao/paste/...[huge string]' at Module.lstatSync (node:fs:1713:25) at robustRealpath (/Users/huyitao/gemini-cli/packages/core/src/utils/paths.ts:389:25) at resolveToRealPath (/Users/huyitao/gemini-cli/packages/core/src/utils/paths.ts:372:10) at checkPermissions (/Users/huyitao/gemini-cli/packages/cli/src/ui/hooks/atCommandProcessor.ts:191:28)

TL;DR

To fix the CLI crash, add a maximum length check before calling fs.lstatSync in resolveToRealPath to prevent ENAMETOOLONG errors.

Guidance

• Identify the maximum allowed path length for the operating system (e.g., 1024 characters on macOS) and add a check in resolveToRealPath to ensure the input string does not exceed this length.
• Modify parseAllAtCommands to handle strings starting with @ as potential literal text if they exceed the maximum path length or cannot be resolved as a path.
• Catch and handle ENAMETOOLONG errors in resolveToRealPath to prevent unhandled promise rejections and provide a graceful fallback.
• Consider adding input validation and sanitization in parseAllAtCommands to prevent similar issues with other types of input.

Example

// In resolveToRealPath (packages/core/src/utils/paths.ts)
const maxPathLength = 1024; // Adjust according to the operating system
if (inputString.length > maxPathLength) {
  // Handle as literal text or throw a custom error
  throw new Error(`Input string exceeds maximum path length: ${inputString}`);
}

Notes

This fix assumes that the ENAMETOOLONG error is the primary cause of the crash. Additional logging or debugging may be necessary to ensure that other issues are not contributing to the problem.

Recommendation

Apply the workaround by adding a maximum length check in resolveToRealPath to prevent ENAMETOOLONG errors, as this is a targeted fix for the identified root cause.