* Fix these
* Update phpstan
* Transform these into their identifiers instead
* Fix custom rule
* License is wrong
* Update these
* Pint fixes
* Fix this
* Consolidate these
* Never supported PHP 7
* Better evaluation
* Fixes
* Don’t need ignore
* Replace trait with service
* Subusers are simply the many to many relationship between Servers and Users
* Adjust to remove ignores
* Use new query builder instead!
* wip
* Update composer
* Quick fixes
* Use realtime facade
* Small fixes
* Convert to static to avoid new
* Update to statics
* Don’t modify protected properties directly
* Run pint
* Change to correct method
* Give up and use the facade
* Make sure this route is available
* Filament hasn’t been loaded yet
* This can be readonly
* Typehint
* These are no longer used
* Quick fixes
* Need doc block help
* Always true
* We use caddy with docker
* Pint
* Fix phpstan issues
* Remove unused import
---------
Co-authored-by: MartinOscar <40749467+RMartinOscar@users.noreply.github.com>
This accounts for poorly configured API clients that try to use cookies for authentication purposes. Treat everything with a session cookie as being a stateful request from the front-end.
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>
