v4.4.0 topology destroyed error

[perrin4869]

Hi, I just updated to v4.4.0, and now I see an error during my tests, although I really don't know what the cause could be:

Unhandled rejection MongoError: topology was destroyed

Any clues what could be causing this? I tested v4.3.7 and the error wasn't there.

[vkarpov15]

I suspect this is related to #3790, because now the .connect() and close() methods now return ES2015 promises. I think the solution will be to just make it so that these functions don't return promises if you specify a callback to minimize impact.

[vkarpov15]

Also, can you provide a code sample or show how you're connecting?

[perrin4869]

Actually, it's a bit convoluted, starting and closing connections before each unit test, I'll try to isolate the problem and report back though! The test still passes btw, so mongoose is working

[perrin4869]

Made a repository with the problem almost isolated: https://github.com/perrin4869/mongoose_topology_error

[vkarpov15]

Thanks for the detailed repro instructions, turns out this warning was due to the fact that we had an unhandled rejection internally when model init calls ensureIndexes(), which returns a promise as of #3795. Nothing to really worry about. The above commit will make the warning go away.

[perrin4869]

Awesome, looking forward to 4.4.2 then, thanks!!!