Setup;
"laravel/framework": "^8.0",
"laravel/vapor-core": "^2.0",
"laravel/telescope": "^4",
"php": "^7.4",
So a little time ago I was noticing some strange exceptions in the telescope exception logging. It's showing 'Class ... not found' but not for a specific class, this includes models Illuminate classes, Service providers and so on.
My findings are those exceptions probably come from running a command. I do not know which command is triggering this, it only shows up on production environment as well, probably because it's being used more than the other environments. I based this on the stack trace starting with artisan.
Here is a screenshot of some exceptions (these are just some, it's a whole list of random exceptions)
P.S the website/app is working as expected, the only thing is if I come back the next morning to work, I see those exceptions.
I tried reinstalling composer packages and a re-deploy without any effect.
Does anyone have an idea of what might cause these exceptions?
This is my post-update-cmd
"post-update-cmd": [
"php artisan clear-compiled",
"php artisan optimize",
"php artisan view:clear",
"php artisan config:clear",
"php artisan route:clear",
"@php artisan vapor-ui:publish --ansi",
"@php artisan telescope:publish --ansi"
],