114afb8646
There is a bug in the design of the application that affects users who encounter an exception under certain code pathways who are using the database to maintain their sessions. What is happening is that a transaction is started, and I made the mistake of just assuming it would auto-rollback once the exception was caught by the handler. This is technically true, since once the request terminates the transaction is discarded by the SQL server. However, this also means that the session data set on that request would not be persisted as it runs in a middleware termination function, after the transaction is started. Theoretically this would also affect any other terminable middleware as well, but the session is the only one I can think of right now Co-Authored-By: Oreo Oreoniv <zkoz210@users.noreply.github.com> Co-Authored-By: Stepan Fedotov <trixterthetux@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| Http | ||
| Model | ||
| Repository | ||
| Service | ||
| Transformer | ||
| AccountNotFoundException.php | ||
| AutoDeploymentException.php | ||
| DisplayException.php | ||
| Handler.php | ||
| PterodactylException.php | ||