Skip to content

Handle NOT_FOUND error for missing runners in CLI#918

Open
hanchchch wants to merge 1 commit intomainfrom
claude/fix-runner-error-message-ESire
Open

Handle NOT_FOUND error for missing runners in CLI#918
hanchchch wants to merge 1 commit intomainfrom
claude/fix-runner-error-message-ESire

Conversation

@hanchchch
Copy link
Collaborator

Summary

Added specific error handling for when a runner is not found in the FAL CLI, providing a clearer error message to users instead of a generic unavailable error.

Key Changes

  • Added a new error condition to check for grpc.StatusCode.NOT_FOUND before the existing UNAVAILABLE check
  • When a runner is not found, the CLI now displays a user-friendly error message: "Error: Runner '{runner_id}' not found."
  • Preserved existing error handling for UNAVAILABLE status as a fallback case

Implementation Details

The change improves the error handling flow in the stream_inputs() function by distinguishing between two different gRPC error scenarios:

  1. NOT_FOUND: Indicates the runner doesn't exist (new behavior)
  2. UNAVAILABLE: Indicates the runner service is temporarily unavailable (existing behavior)

This provides better user experience by giving specific feedback when a runner cannot be found versus when the service is unavailable.

https://claude.ai/code/session_01H4pXbeFhJ3xREeuriHshca

When a runner doesn't exist, the CLI now shows "Runner '<id>' not found"
instead of a generic "Connection error" with the server's error details.
This gives users a clear, actionable message.

https://claude.ai/code/session_01H4pXbeFhJ3xREeuriHshca
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.

2 participants