Lars-Erik Roald

No, I don't think I did. I turned off detail

I think I used another tool to calculate the actual difference, [fast-json-patch](https://www.npmjs.com/package/fast-json-patch) And just used on-change to signal a change happened.

I am having similar issue on windows 64 bit server. But I am not using electron. It was working fine on node 16, but when upgrading to node 20 this...

Sorry, I installed node 21 by a mistake on the server. Thank you.

Do you know the status of this issue ? Will #36 solve the problem ?

You can use [msnodesqlv8](https://github.com/TimelordUK/node-sqlserver-v8) for windows authentication. Alternatively, you can use [rdb ORM](https://github.com/alfateam/rdb) that supports both tedious and msnodesqlv8. Just use rdb.mssqlNative(..) instead of rdb.mssql(...) and install msnodesqlv8 first. You...

It could be related to winston logger blocking the process. I have deactivated the winston logger just to eliminate. Waiting for what is gonna happen tonight. https://github.com/winstonjs/winston/issues?q=is%3Aissue+hang+is%3Aopen https://github.com/winstonjs/winston/issues/1364

It was still blocking tonight with winston logger deactivated.

I tried replacing generic-pool with https://github.com/vincit/tarn.js/ , but blocking still occurs. It could be related to my own code, but I just can't see how...

The sleeping/blocking connection is in the middle of a transaction and is supposed to receive a commit. But it never happens. It seems to be some kind of (dead)lock in...