Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: RPC mode does not honor timeout #1230

Merged

Conversation

aepfli
Copy link
Member

@aepfli aepfli commented Feb 19, 2025

During the refactoring of the connection the timeout for unary calls got lost. This adds the timeout back into the mix.

TODO:

How to test:

currently one e2e test is failing, which should fail, as this one should actually not work for rpc.

blocked by open-feature/flagd-testbed#229

aepfli added a commit to open-feature/flagd-testbed that referenced this pull request Feb 19, 2025
aepfli added a commit to open-feature/flagd-testbed that referenced this pull request Feb 19, 2025
@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch from 50cb01b to 9240d70 Compare February 19, 2025 07:56
aepfli added a commit to open-feature/flagd-testbed that referenced this pull request Feb 19, 2025
@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch 2 times, most recently from ee7ed54 to 7deaff5 Compare February 19, 2025 10:30
@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch from 7deaff5 to 506c587 Compare February 19, 2025 10:38
@aepfli aepfli marked this pull request as ready for review February 19, 2025 10:46
@aepfli aepfli requested a review from a team as a code owner February 19, 2025 10:46
aepfli added a commit to open-feature/flagd-testbed that referenced this pull request Feb 19, 2025
@toddbaert
Copy link
Member

@aepfli while we are here, can we add a deadline to the getSyncMetadata call in the in-process as well?

@aepfli
Copy link
Member Author

aepfli commented Feb 19, 2025

@aepfli while we are here, can we add a deadline to the getSyncMetadata call in the in-process as well?

I tried to add it, but it breaks our reconnection tests in a strange way.

If we want to add it, I think it is worth to explore this separately. I also opened an issue with discussion points to start with. Eg. The sync metadata does not have to be part of our loop, we could do this everytime the channel is reestablished. Anyways I think we should discuss this, and define this more precisely, as this could be also the way to go for other languages

See: #1231

aepfli added a commit to open-feature/flagd-testbed that referenced this pull request Feb 19, 2025
Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

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

This seems like a step in the right direction.

I've made a related proposal here: #1231

@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch from 506c587 to 416060f Compare February 19, 2025 15:02
@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch from 416060f to d0fa1ad Compare February 20, 2025 14:26
During the refactoring of the connection the timeout for
unary calls got lost. This adds the timeout back into the
mix.

TODO:
- [ ] adapt gherkin tests for contextEnrichment to do handle stale seperately for file and inprocess

Signed-off-by: Simon Schrottner <[email protected]>
@aepfli aepfli force-pushed the fix/RPC_mode_not_using_deadline branch from d0fa1ad to d898ace Compare February 20, 2025 14:30
@aepfli aepfli enabled auto-merge (squash) February 24, 2025 14:37
@aepfli aepfli merged commit 5b509d0 into open-feature:main Feb 24, 2025
5 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.

6 participants