rpc: nicer error message for RPC server crash #14076
Merged
+18
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Currently the RPC error throws a cryptic-looking error if the remote side crashes because the generic
GGML_ASSERT
macro is used.This PR just adds a simple, RPC-server-specific macro that has the same behavior as
GGML_ASSERT
but prints a slightly nicer message.Note that the error message assumes that the only reason an invalid
status
would be returned is a RPC server crash or malformed payload. I'm happy to change the message if there are other edge-cases we want to cover.Before:
After:
Testing
Tested by specifying only the
-ctk q4_0
flag (without-ctv q4_0
and withoutGGML_CUDA_FA_ALL_QUANTS
) and running an example prompt.Accidentally omitting this flag and getting the cryptic error is what motivated this PR.