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.
Description
This pull request introduces changes to ensure consistent gRPC message size limits across various backends and client implementations. The updates set maximum message sizes to 50MB for sending, receiving, and overall message length. These changes improve the handling of large payloads and prevent errors caused by exceeding default gRPC limits.
Backend Updates
grpc-server.cpp
): AddedSetMaxMessageSize
,SetMaxSendMessageSize
, andSetMaxReceiveMessageSize
to set the maximum gRPC message size to 50MB.serve
functions in multiple files (e.g.,autogptq
,bark
,coqui
,diffusers
,exllama2
,faster-whisper
,kokoro
,rerankers
,transformers
,vllm
) to include gRPC options formax_message_length
,max_send_message_length
, andmax_receive_message_length
, all set to 50MB. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Client Updates
client.go
):HealthCheck
,Embeddings
,Predict
,LoadModel
,GenerateImage
,TTS
,AudioTranscription
, etc.) to includegrpc.WithDefaultCallOptions
for settingMaxCallRecvMsgSize
andMaxCallSendMsgSize
to 50MB. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]Notes for Reviewers
Signed commits