Fix stuck transaction in spec
It seems that the connection we obtained was reused, even though we expected to have a separate one for the initial lock. It may be related to the changes how ActiveRecordSecond is being set up in Ruby3.
Showing
Please register or sign in to comment