fix(data-service): disable utf8 validation when retrieving metadata compass needs in order to function COMPASS-8517 #6531
Conversation
| }, | ||
| ]) | ||
| ], | ||
| { enableUtf8Validation: false } |
There was a problem hiding this comment.
I just added this option which triggered the whole aggregation to be reformatted by prettier.
There was a problem hiding this comment.
Added this one here because the user's error log file contained a lot of aggregate failed commands and we have a hunch it might be this one.
…rgue about them one by one
|
I'm reasonably sure that it is the hostname that can (under some edge cases) contain non-ascii characters that then gets passed through as part of the output of commands that include the hostname in the response and then the driver throws because the server's response fails utf8 validation. Disabling utf8 validation for these commands should cover it as a workaround and it should be low-risk. For a reproduction on linux, see https://jira.mongodb.org/browse/SERVER-97683 |
Anemy
changed the title
See https://jira.mongodb.org/browse/SERVER-97683
This can make compass unusable because we use commands that will include the hostname. It is reasonably safe to just turn off utf8 validation in those cases. We still leave it on when reading/writing documents and therefore users aren't at risk of writing back broken data to their database.