You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest Octane release seems to have a regression related to 7fecb1d.
Workers crash after serving an initial request. Workers stop crashing when I take any of the following actions.
Downgrade to Octane 1.5.1
Remove 'session' and 'session.store' from the octane.warm configuration
Remove \Laravel\Octane\Listeners\GiveNewApplicationInstanceToSessionManager::class as a RequestReceived listener
I'm having trouble finding any useful error output from my local environment (nothing is written to the Laravel log). However, after deploying 1.5.2 to the Vapor environment our logs filled w/ error messages like the following.
{
"exception": {
"class": "Illuminate\\Contracts\\Container\\BindingResolutionException",
"message": "Target class [config] does not exist.",
"code": 0,
"file": "/var/task/vendor/laravel/framework/src/Illuminate/Container/Container.php:916",
"previous": {
"class": "ReflectionException",
"message": "Class \"config\" does not exist",
"code": -1,
"file": "/var/task/vendor/laravel/framework/src/Illuminate/Container/Container.php:914"
}
}
}
Steps To Reproduce:
Octane 1.5.2
Octane 1.5.1
The text was updated successfully, but these errors were encountered:
Description:
The latest Octane release seems to have a regression related to 7fecb1d.
Workers crash after serving an initial request. Workers stop crashing when I take any of the following actions.
octane.warm
configuration\Laravel\Octane\Listeners\GiveNewApplicationInstanceToSessionManager::class
as aRequestReceived
listenerI'm having trouble finding any useful error output from my local environment (nothing is written to the Laravel log). However, after deploying 1.5.2 to the Vapor environment our logs filled w/ error messages like the following.
Steps To Reproduce:
Octane 1.5.2
Octane 1.5.1
The text was updated successfully, but these errors were encountered: