Skip to content

Conversation

Mr3zee
Copy link
Member

@Mr3zee Mr3zee commented Aug 4, 2025

Subsystem
gRPC

Problem Description
Tests with streaming were not working

Solution
Closer rewrite the code and see that Ready has one more property for overall client/server readiness
Disclaimer: I have absolutely no idea why this fix works

@Mr3zee Mr3zee requested a review from Jozott00 August 4, 2025 20:48
@Mr3zee Mr3zee self-assigned this Aug 4, 2025
@Mr3zee Mr3zee added the bug Something isn't working label Aug 4, 2025
@Mr3zee
Copy link
Member Author

Mr3zee commented Aug 4, 2025

oooooooh I think I know now, but it is cursed

@Jozott00
Copy link
Collaborator

Jozott00 commented Aug 5, 2025

Is it because the isReady() state doesn't necessarily turn false when sending one message? Which means that it stays true, but as we previously relied on the onReady() invocation (which is not triggered a second time, as isReady() never turned false), the second message is never processed/sent as ready.suspendUntilReady() doesn't return.

@Mr3zee
Copy link
Member Author

Mr3zee commented Aug 5, 2025

@Jozott00 yes, I thought each .request invokation changed the ready state but it is not

@Mr3zee Mr3zee merged commit 525a1ee into grpc-common Aug 5, 2025
2 of 3 checks passed
@Mr3zee Mr3zee deleted the grpc-services branch August 5, 2025 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants