-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throwing exception with FrankenPHP causes crash with 'Undefined array key "msg"' #803
Comments
Thanks. I tried sending in a fix here: #804 |
Can't reproduce the issue. Can you create an open-source repository, with a fresh Laravel application + Octane, where it's easy to reproduce the issue locally for me? Please re-open the issue once you have that ready. Thanks! |
Fwiw, facing the same issue while moving an existing (old, but updated) laravel 10 project to frankenphp. |
Same problem here. Can we open the issue ? |
I need a way to reproduce the issue. Can someone facing this issue helping with it? |
Can you create an open-source repository, with a fresh Laravel installlation and Octane, where I can clone the repository locally to reproduce the issue? |
I cannot work on this today or tomorrow, but I will see if I can do this on Sunday or Monday if no one else gets to it first. |
Octane Version
2.2.6
Laravel Version
10.28.0
PHP Version
8.2.7
What server type are you using?
FrankenPHP
Server Version
1.0.2
Database Driver & Version
No response
Description
The easiest way to reproduce this is to start the application without a
.env
file (or any other form of configuration). This will cause it to throw anIlluminate\Encryption\MissingAppKeyException
.Running
php artisan octane:start
starts the server, but produces the following error when trying to visit a page in the web browser:I added
dump($debug);
above that line, and here is the output that I get (before the same crash shown above):There is a
msg
in the first JSON body, but there is amessage
in the second one.I would expect that the error is caught and displayed, not that the application would crash without showing the actual reason for the crash. (No error is logged in
storage/logs/laravel.log
either, as far as I can tell.Steps To Reproduce
.env
file.php artisan octane:start
The text was updated successfully, but these errors were encountered: