Cursor session id (none) is not the same as the operation context's - release 5.0.15 broken

bug with the latest mongoose (guess the underyling problem lies in mongodb-core though).

What is the current behavior? After upgrading to 5.0.15 no queries are running anymore:

Unhandled rejection MongoError: Cursor session id (none) is not the same as the operation context's session id (f6a28f6f-7dfa-424d-8691-fd40b12733ee - 0rbp3hXFaGQzW/eEz2QZrZ7et36CzL3bnxgnuRX9rEo=)
    at /home/simon/Dev/Web/hokify-server/node_modules/mongodb-core/lib/connection/pool.js:598:61
    at authenticateStragglers (/home/simon/Dev/Web/hokify-server/node_modules/mongodb-core/lib/connection/pool.js:516:16)
    at Connection.messageHandler (/home/simon/Dev/Web/hokify-server/node_modules/mongodb-core/lib/connection/pool.js:552:5)
    at emitMessageHandler (/home/simon/Dev/Web/hokify-server/node_modules/mongodb-core/lib/connection/connection.js:309:10)
    at Socket.<anonymous> (/home/simon/Dev/Web/hokify-server/node_modules/mongodb-core/lib/connection/connection.js:452:17)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)

If the current behavior is a bug, please provide the steps to reproduce. Just upgrade it, didn’t change anything else.

What is the expected behavior? Work the same way like it does with 5.0.14. Downgrading to .14 solves all problems instantely.

Please mention your node.js, mongoose and MongoDB version. node v9.3.0 mongoose 5.0.15 mongodb 3.6.4

[vkarpov15]

As a workaround, try passing the skipSessions option to the failing query.

MyModel.find({}, null, { skipSessions: true });

The MongoDB driver implicitly creates sessions if you’re connected to MongoDB 3.6 running WT, that option will turn off that behavior. Should help with this issue.

[simllll]

New mongodb-core got released today, as soon as mongoose upgrades to 5.0.18 tthe issues should be done/gone!

Thanks