Skip to content

Conversation

@wdauchy
Copy link
Contributor

@wdauchy wdauchy commented Dec 26, 2025

Commit Message:
Previously, MuxDemux::multicast accepted a single StreamOptions for all backends, which meant per-backend timeouts couldn't be configured. The mcp_router worked around this by using the maximum timeout across all backends.

This change adds an optional options field to MuxDemux::Callbacks, allowing callers to specify per-backend StreamOptions. When set, these options override the default options passed to multicast().

The mcp_router now uses this feature to set proper per-backend timeouts instead of the max-timeout workaround.
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@repokitteh-read-only
Copy link

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #42777 was opened by wdauchy.

see: more, trace.

@wdauchy wdauchy force-pushed the mux branch 3 times, most recently from c67756a to 23bf28c Compare December 26, 2025 08:20
@wdauchy wdauchy marked this pull request as ready for review December 26, 2025 09:41
Copy link
Member

@botengyao botengyao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks @wdauchy!

@botengyao
Copy link
Member

/retest

Previously, MuxDemux::multicast accepted a single StreamOptions for all
backends, which meant per-backend timeouts couldn't be configured. The
mcp_router worked around this by using the maximum timeout across all
backends.

This change adds an optional `options` field to MuxDemux::Callbacks,
allowing callers to specify per-backend StreamOptions. When set, these
options override the default options passed to multicast().

The mcp_router now uses this feature to set proper per-backend timeouts
instead of the max-timeout workaround.

Signed-off-by: William Dauchy <[email protected]>
@botengyao botengyao merged commit b557e92 into envoyproxy:main Dec 30, 2025
24 checks passed
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