• In ScanOverRandomInvalidDataAggRequest, the runCommand will fail because when loading the initial batch of results because it will detect invalid BSON. The solution here seems to be to catch and accept an invalid BSON error

• In the same test, we will fail the following assertion with a ‘NamespaceExists’ error. From what I gather, this is likely an issue with the maintenance of the lifetime of a virtual collection. Have you seen this sort of issue before?

I think the root cause is basically same for two issues. The error occurs at the DBDirectClient side by the invalid cursor batch return data and when the issue occurs, we don’t have a chance when the server-side virtual collection clean-up logic kicks in. I think the best course of action for now is to remove two test cases with a TODO. I think I’d better to write two test cases in jstests so that the server-side clean-up logic can be executed properly.

error message:

ScanOverRandomInvalidDataAggRequest: InvalidBSON: incorrect BSON length in element with field name 'cursor.firstBatch.1.2.2' in object with unknown _id

I don't think these two tests are so valuable and so set the priority to minor.