Pieter Hoste

> yes - we should look for way to clear specific categroy or detail page cache instead of full cache flush, If you do a full reindex, it will go...

1. probably not, unless you write some custom code yourself (or find a module that has already done that) 2. yes, don't run a full reindex manually and let the...

Not stale, somebody on Slack complained about this issue one day ago. There's even a PR open for this: https://github.com/magento/magento2/pull/32366 @sidolov, @Den4ik, @gabrieldagama: can we have somebody verify this please?...

Probably fixed by https://github.com/magento/magento2/commit/76362cfc120153255e7f1079d62e47eb3dcc96eb ?

Might be better to define a conflict with this specific version, so you don't pin the version 1.5.5 in your `composer.json` file and forget about removing it again in the...

@PaulWatt, just downgrade `colinmollenhour/php-redis-session-abstract` to version 1.5.5 and wait until @colinmollenhour has had some time to look into https://github.com/colinmollenhour/php-redis-session-abstract/issues/58

@chernenm, @jorgb90: I believe we can close this issue, now that version 1.7.0 was released which fixes this, right?

@engcom-Dash: that's not the point, this was just the easiest way I could find to demonstrate the problem 😉 This will most likely happen in the real world where you...

I think this duplicates: - https://github.com/magento/magento2/issues/37935 (reported against 2.4.4-p5) - https://github.com/magento/magento2/issues/38150 (reported against 2.4.5-p2) I would still consider it a bug that you are allowed by composer to install these...

For some reason, this PR wasn't marked as merged, even though (some of) the code was merged (via cherry-picks) recently as part of this bigger merge: https://github.com/magento/magento2/commit/0c53bbf7b6712c9b979a1c7ee71594ce523d78e3