Hi,
> I've come across a scenario where unchanged code works on 5.6/MP1 such that
> through various routes we twice tie a session object within a request's
> life. Under the hood it seems to invoke get_lock(id) in the DB on when
> doing the tie. I'm not exeactly sure where but I assume the second
I'm working on a combined 5.6->5.8 and MP1->MP2 migration.
I've come across a scenario where unchanged code works on 5.6/MP1 such
that through various routes we twice tie a session object within a
request's life. Under the hood it seems to invoke get_lock(id) in the DB
on when doing the tie.
