its
Hey, can you please provide more information about your app? From the code example it doesn't seem like a standard Laravel app.
Thanks, this is very useful, will return to this tomorrow.
Hey, I've finally got around to check this out. This should now be fixed in master and will be released soon, sorry for the long wait. This was actually caused...
Glad you like it, this is now released as part of Clockwork 5.1.7.
thanks! we actually already do support n+1 query detection in the laravel integration. check out this blog post to see what it looks like - https://underground.works/blog/clockwork-4.0-released-with-ui-improvements-requests-search-and-more we do the detection...
1 this implementation is specifically aimed at programmer errors when using eloquent, eg. missing eager loads, etc. we actually hook into eloquent and compare stack traces and stuff, we don't...
hey, will check this out soon, in the meantime you can turn off the duplicate queries detection: ``` CLOCKWORK_DATABASE_DETECT_DUPLICATE_QUERIES=false ```
Released Clockwork 4.1.7 with an additional check to avoid the crash. I would still like to know why the stack frame object would be null, but I guess that will...
Ah, it's a static call so there is no object instance. Very useful, will investigate further, thanks.
Hey, is the 404 error returned by Laravel or your web server?