its comments

Results 176 comments of

its

Argument 6 passed to Symfony\Component\HttpFoundation\Cookie::__construct() must be of the type boolean, null given, called in vendor/itsgoingd/clockwork/Clockwork/Support/Laravel/ClockworkSupport.php on line 438

Hey, thanks for the traces, we definitively want to keep supporting Laravel 5.6, I'll have a fix ready soon.

Argument 6 passed to Symfony\Component\HttpFoundation\Cookie::__construct() must be of the type boolean, null given, called in vendor/itsgoingd/clockwork/Clockwork/Support/Laravel/ClockworkSupport.php on line 438

Fixed in Clockwork 5.2.

Unable to Expand Array/Object with Key Starting with Numeric

Hey, thanks for the report, will fix in the next release.

commandExecuted - no output in extension

Hey, I've fixed a bug, that could cause non-http requests to not show up in the Clockwork extension. Can you give `dev-master` a try?

commandExecuted - no output in extension

Not really. To show commands in the extension, we take the last shown request's id and then poll the Clockwork rest api that's part of your app, to return any...

commandExecuted - no output in extension

Fix included in Clockwork 5.2.

Add other server indicators on sidebar

Hey, I'll consider adding these in a future release. Thanks.

Redis::pipeline calls not being instrumented

Hey, thanks for the heads up. *Note, the following is based only on reading the Laravel code, I haven't tested anything.* Looks like for pipelines, they pass the PhpRedis client...

Profiler Tab stuck on "Loading profile"

Hey, you can try changing the `xdebug.profiler_output_name` setting if you are running into an issue with multiple profiles being written to the same file, we solved a similar issue here...

Profiler Tab stuck on "Loading profile"

Yeah, having some diagnose command would be cool at some point. For starters, we should suggest changing the `xdebug.profiler_output_name` in the docs, as the default value does not make sense...