SERVER-130823ClosedFixed
Change stream with update lookup can trip server assertion
We have a test in the mongosync codebase that sometimes (extremely rarely) trips an assertion in the server. The test opens a change stream with {{fullDocument: updateLookup}}, updates some documents in a collection, then drops that collection. Sometimes in CI this test fails because the change stream trips a tassert in the server, with an error like: This seems like a bug in the express engine: it seems like it shouldn't be possible to observer a state where a collection exists but do