[DRIVERS-2151] "operation fails with maxWireVersion < 8" fails with aggressive mongocryptd spawning Created: 07/Aug/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Driver Changes: Needed

 Description   

Now that drivers are supposed to aggressively start mongocryptd when constructing a MongoClient, the "operation fails with maxWireVersion < 8" no longer is easily implementable. The driver tries to start mongocryptd and since we're testing against a 4.0 server there is no mongocryptd available to start. So MongoClient throws the exception in the test set up and we don't get to the expected exception.

I suggest we skip this test until we figure out a way to that we can make it pass.



 Comments   
Comment by Githook User [ 07/May/20 ]

Author:

{'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}

Message: Reinstated client-side-encryption/maxWireVersion.json but indicate its waiting on SPEC-1403
Branch: 3.12.x
https://github.com/mongodb/mongo-java-driver/commit/d14d40b0419d4ab3c03af46d12f3ab7cc1c47590

Comment by Githook User [ 22/Apr/20 ]

Author:

{'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}

Message: Reinstated client-side-encryption/maxWireVersion.json but indicate its waiting on SPEC-1403
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/c9a651380be948b66090070f05fd846127596e22

Comment by Jeffrey Yemin [ 07/Aug/19 ]

shane.harvey has perhaps a better suggestion: suppress any error from starting the mongocryptd process (logging it if possible).

Generated at Thu Feb 08 08:24:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.