Closed jeffery812 closed 3 years ago
Actually, there were cases in 1.3 where it actually failed to lock when needed. 1.4 fixed that.
As to the deadlock, there's not enough information here for me to attempt to debug this. I suggest looking at the stack trace to see if you can determine where and under what circumstances you might be deadlocking.
No response so closing.
In Resolver 1.4.0, when I try to resolve a dependency, it get stuck at
lock.lock()
, it seems it get dead lock here. But it worked very well in 1.3.0. Please kindly have a look, thank you.