MONGOCRYPT-820 bypass serverStatus from auto-encryption
#1028
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Set to 3600 seconds (60 minutes) to match comment. Fixes error from `evergreen validate`: ``` exec timeout (216000) is too high ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bypasses
serverStatusfrom query analysis instead of erroring.As a drive-by fix, reduces the
exec_timeout_secsinrelease-python-linuxto fix an error observed byevergreen validate:Background
libmongocrypt errors if trying to auto-encrypt a command not explicitly listed. This is intended to err towards safety: if libmongocrypt is unsure if the command might have values to encrypt reject it rather than risk sending plaintext that should be encrypted. serverStatus is not expected to have values needing encryption.