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

(PDB-5663) Sync version +1 to improve sync request timeout handling #3823

Merged

Conversation

rbrw
Copy link
Contributor

@rbrw rbrw commented Jun 14, 2023

Increment the sync version so that sync requests from newer servers that specify a query timeout will receive a more meaningful message that indicates the version mismatch, rather than a more generic crash on an unexpected parameter.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@rbrw
Copy link
Contributor Author

rbrw commented Jun 14, 2023

One way we might handle it.

@rbrw rbrw force-pushed the pdb-5663-improve-timeout-sync-request-responses branch 2 times, most recently from e3693fb to dc5c203 Compare August 4, 2023 16:21
Increment the sync version so that sync requests from newer servers
that specify a query timeout will receive a more meaningful
message that indicates the version mismatch, rather than a more
generic crash on an unexpected parameter.
@rbrw rbrw force-pushed the pdb-5663-improve-timeout-sync-request-responses branch from 857ae27 to 0ef376a Compare August 8, 2023 19:46
@rbrw rbrw marked this pull request as ready for review August 8, 2023 19:50
@rbrw rbrw requested review from a team as code owners August 8, 2023 19:50
@rbrw rbrw merged commit bc74da8 into puppetlabs:main Aug 9, 2023
8 of 9 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.

3 participants