Mikro ORM check returns healthy although not connected about terminus HOT 7 OPEN

Hi @BrunnerLivio , I tested the @nestjs/[email protected] in one of our services, and it works as expected.
I tested these cases:

1. The database connection cannot be established. (I intentionally set a wrong port for DB to test this.)
2. Time out error ( I set timeout to 1ms to test this)

from terminus.

This has now been officially released with 10.2.2 🎉

from terminus.

Can you create minimal reproduction in a cloneable git repository?

from terminus.

I can confirm - we discovered the same issue today.
I kill DB container, but health checks returns "up" forever despite of that.

from terminus.

Hi, we face the same bug in our services. What is interesting is that the first pingCheck after the server starts will return an error (which is right), but all ping checks after it will return up

from terminus.

We face the same problem too.

from terminus.

I created a new beta release, would you mind checking? NPMJS link, install via:

npm i @nestjs/[email protected]

from terminus.