cyppe
cyppe
Nothing to add more than that I am also seeing the same issue. Only for php artisan schedule:run, and only when it runs in cron. Works fine when I run...
That is amazing. I can confirm that using Redis::get('foo'); inside the pipeline closure really works. And it still uses the pipeline method. I was afraid it would go back to...
Or actually.. I just measured it it in wrong way. In bulk each event contains a lot of rows. So It's actually processing on average 40.000 rows for me. So...
Last addition: For big tables, or rather, wide tables with a lot of columns it's pretty slow anyway. But it's more data so shuffle around so I guess it makes...
Same error here. As soon as I add 'gd' some other extension fails. A part of my Dockerfile as example where you can (hopefully) reproduce it too. It worked fine...
Update: Probably same as previous mentions, there has been a new php 8.3 release since my last successful build. Will try to lock it to 8.3.3 instead of 8.3.4. Update...
I can confirm I have had the same issue. It behaves very strange when reaching maxmemory. It always accepts write, and in many cases it seems like it works fine...
Yeh thanks, but I use it not only for cache so auto eviction is not an option here. Would be better if it rejects operations similar to redis if noeviction...
I have this problem, so hope it's possible to merge this soon.
I was there and looked, but that is the actual pipeline method from phpredis extention. And that signature is correct. So the problem is that somehow phpstan thinks we call...