Skip to content

Conversation

donaldsharp
Copy link
Member

Currently when the fpm_listener attempts to read say X bytes it may only get Y( which is less than X ). In this case we should assume that the dplane_fpm_nl code is just being slow, as that we know it is possible for it to send a partial fpm message. Let's just loosen the constraints a bit and allow data to flow.

@donaldsharp
Copy link
Member Author

ci:rerun

Currently when the fpm_listener attempts to read say X
bytes it may only get Y( which is less than X ).  In this
case we should assume that the dplane_fpm_nl code is just
being slow, as that we know it is possible for it to send
a partial fpm message.  Let's just loosen the constraints
a bit and allow data to flow.

Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Copy link
Contributor

@mjstapp mjstapp left a comment

Choose a reason for hiding this comment

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

sure - keep trying

@mjstapp mjstapp merged commit 75bc4a4 into FRRouting:master Feb 12, 2025
13 checks passed
@donaldsharp donaldsharp deleted the fpm_keep_on_trying branch July 30, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants