You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PHP 8.4.3 (cli) (built: Jan 15 2025 01:03:17) (NTS)
Copyright (c) The PHP Group
Built by Homebrew
Zend Engine v4.4.3, Copyright (c) Zend Technologies
with Xdebug v3.4.1, Copyright (c) 2002-2025, by Derick Rethans
with Zend OPcache v8.4.3, Copyright (c), by Zend Technologies
Error
Object of class Closure could not be converted to string
at vendor/open-telemetry/opentelemetry-auto-laravel/src/Watchers/RedisCommand/Serializer.php:75
71▕
72▕ // In some cases (for example when using LUA scripts) arrays are valid parameters
73▕ $paramsToSerialize = array_map(function($param) { return is_array($param) ? json_encode($param) :$param; }, $paramsToSerialize);
74▕
➜ 75▕ return$command.''. implode('', $paramsToSerialize);
76▕ }
77▕ }
78▕
+23 vendor frames
Additional context
Horizon runs this code snippet:
Then it, as event, catched via RedisCommandWatcher with parameter - pipeline closure. Closure cannot be converted as string.
Pipeline isnt Redis command, its internal Illuminate/Redis/Connections/PhpRedisConnection construction, but it used for event dispatching also.
Probably, we need drop serialization for "Pipeline" call, as we can't extract data from it correctly
The text was updated successfully, but these errors were encountered:
Describe your environment
Steps to reproduce
Run
php artisan horizon
What is the expected behavior?
No errors
What is the actual behavior?
Additional context
Horizon runs this code snippet:
Then it, as event, catched via RedisCommandWatcher with parameter - pipeline closure. Closure cannot be converted as string.
Pipeline isnt Redis command, its internal Illuminate/Redis/Connections/PhpRedisConnection construction, but it used for event dispatching also.
Probably, we need drop serialization for "Pipeline" call, as we can't extract data from it correctly
The text was updated successfully, but these errors were encountered: