I'm trying to figure out a bug I've reported here: https://github.com/Automattic/mongoose/issues/6504
And finally managed to track it down a little more, it must be related to mongodb-native-driver 3.0.4 and 3.0.5. It works with 3.0.4, and doesn't with 3.0.5. I've checked the changeset to track it down, but unfortuantely I'm super unfimilar with the node-mongodb-native code .
But I stumpled up onto something that "could" be related:
If you look at the changeset, you ysee in lib/collection.js the parameter of excecuteOperation is changed from returnsCursor to skipSessions, but "returnCursors" flag is also used in lib/utils.js, so this code part is at least definilty called as returnCursors is not set and can (as far as I can see never be set at all). Is this check then necessary or is this a wrong check?
I've tried to revert the call of the excuteOperation to see if affects my bug, unfortuantely it didn't change anything. It seems it is related to the session support at all, maybe even a mongodb bug. Is there any chance to tell a recent driver version that my topology "doesn't support" sessions? So I could at least nail it down to the session . Maybe I'm also affected of https://jira.mongodb.org/browse/SERVER-34810