Marc Bennewitz

@thomasvargiu this issue is not about apcu_bc, this is about the apc compatibly layer of the zend data cache (part of zend server)

@thomasvargiu Needs to be checked with the current Zend Server version if the problem still persist. If so it should either be fixed (FZ or Zend Server) or at least...

PSR-16 > ... If the underlying implementation does not support TTL, the user-specified TTL MUST be silently ignored. ... I have the feeling that what PSR-16 defines here could be...

OK there is a workaround but it's still super hard to create a useful output as well as read the format to understand what's going on. `%{%%FT%%T%%z}t` This basically escapes...

As already told in zendframework/zend-cache#95 - It's a bug in zend-cache that will be addressed by zendframework/zend-cache#96 - In my opinion a serializer (all of `zend-serializer` and `zend-json`) should throw...

@sasezaki the caching should also be moved into the adapters because the adapter only know how to cache paginater results. I think the issues for that are in the zf2...

@sasezaki the caching should also be moved into the adapters because the adapter only know how to cache paginater results. I think the issues for that are in the zf2...

@sasezaki @Ocramius I agree that the caching issue is not part of this PR but it should be addressed in another PR before v3.

According to this [table](https://webassembly.org/features/) the Memory64 and bigint proposals are available in chrome 133 (4. Februar 2025) and ff 134 (7. January 2025) without feature flag. Maybe it's worth giving...

@aJanuary > fwiw, this seems to be resolved in 8.0.38-debian I can confirm it's fixed with `8.0.38-debian`. Any chance to get the version `8.0.37-debian` fixed as well ? -> We...