Indicate cause of "no such file" error when failing to spawn mongocryptd

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Rust Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      When a client configured for auto encryption fails to spawn mongocryptd (e.g. due to not being on the PATH), EncryptedClientBuilder.build() returns the error:

      Error { kind: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), labels: {}, wire_version: None, source: None }
      

      It may be non-obvious (at least, it was to me) what caused this error. Proposal: expand/wrap the error to indicate this is due to failing to spawn mongocryptd.

      To reproduce, see this example

            Assignee:
            Unassigned
            Reporter:
            Kevin Albertson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: