Skip to content

fix: make the gRPC max receive message length configurable (#265) - #528

Merged
s2x merged 2 commits into
masterfrom
fix/265-max-receive-message-length
Sep 9, 2026
Merged

fix: make the gRPC max receive message length configurable (#265)#528
s2x merged 2 commits into
masterfrom
fix/265-max-receive-message-length

Conversation

@s2x

@s2x s2x commented Sep 9, 2026

Copy link
Copy Markdown
Member

Description

Closes #265

Changes

  • Make the gRPC max receive message length configurable instead of relying on the transport default
  • Plumb the new option through the client factory / configuration so it can be set per client
  • Enforce/document the limit consistently with the existing timeout configuration options
  • Add unit tests covering the option plumbing and behavior
  • Document the option in docs/configuration.md

Changelog

Code Review

  • Pending subagent code review

@s2x s2x self-assigned this Sep 9, 2026
@s2x
s2x marked this pull request as ready for review September 9, 2026 21:13
@s2x
s2x force-pushed the fix/265-max-receive-message-length branch from 98a298a to bfbfc16 Compare September 9, 2026 21:13
@s2x
s2x merged commit 7c7195d into master Sep 9, 2026
9 checks passed
@s2x
s2x deleted the fix/265-max-receive-message-length branch September 9, 2026 21:16
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.

[GRPC-06] Configure grpc.max_receive_message_length on created channels

1 participant