Max excution timeouts
I tried a fresh Laravel install and did the first Getting Started steps. When I try to go to /admin/login I get a max execution timeout. Is anyone else getting this error? 30 seconds for a login screen seems excessive.
18 Replies
It really is excessive. Do you have Xdebug or similar running? Does it only happen on Filament login?
yeah the welcome message is super fast
I have xdebug set only on user triggered
Weird. Never encountered this.
after the blade templates are compiled it is a bit faster
but I needed to up the execution time to 120 seconds
So it returns something after 100s? 🤔
yeah I think it works because it has more time to do the blade compilation
This is the message in the laravel.log
I'm using Laravel Valet and PHP 8.1
Can you try a simple Livewire component to check whether it's Filament or Livewire related?
Sure! I've only worked with Inertia + Vue so I need some time
artisan make:livewire should get you started.are there any PHP extensions need perhaps?
a test livewire component also seems fast
it sometimes loads part of the DOM if the max_execution_time is exceeded
Really weird.
yeah I don't get it 😦 Filament looks really promising!
I'm also not sure how to go about debugging this
Turned out xDebug caused it to extremely slow down. Switching it off greatly increases the load time
Something is really weird with your Xdebug. Especially since you mentioned, that you set it to run only on trigger 🤔
yeah I doublechecked it but the settings were correct.. Maybe it has something to do with xDebug + m1 Mac + PHP 8.1?
I'm getting a similar exception when dispatching a job on a resource create. It's meant to be a long-running task that's dispatched, but I'm working locally and using sync at the moment.
I will try to use a different queue to see if that helps.
In the meantime, if anyone can tell me what this 30 second timeout is or where one can change it, I would appreciate it.