- 🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
Re-Rolled The patch For #18 As per the #35 Suggestion .Also add the Inter Diff For The #18 to #37.
- Status changed to Needs review
12 months ago 7:12am 20 February 2024 - Status changed to Needs work
12 months ago 5:07pm 21 February 2024 - Merge request !7090drupal-2872694/2872694-database-backends-cannot : Done the reroll. → (Open) created by prem suthar
- Status changed to Needs review
11 months ago 11:45am 19 March 2024 - Status changed to Needs work
11 months ago 3:41pm 19 March 2024 - First commit to issue fork.
- Status changed to Needs review
11 months ago 11:42am 28 March 2024 - 🇮🇳India immaculatexavier
Fixed #41 🐛 Database backends cannot deal with corrupt serialized data: app completey broken Needs review , and created MR. Kindly review
- Status changed to Needs work
11 months ago 8:55pm 28 March 2024 - Status changed to Needs review
12 days ago 2:38pm 28 January 2025 - 🇺🇸United States cmlara
Pulling in some notes that should be considered:
📌 Make igbinary the default serializer if available, it saves 50% time on unserialize and memory footprint Active is considering swapping the serlaizer, the change to using serialize/unserialize directly may hinder them.
🐛 Json and PHP serializers should throw exception on failure Active is working to have the serializers throw an exception as documented on the API .
I have questions on if returning a cache miss is the correct response here.
If we are having issues unserializing data that implies a significant issue MM in the internal backend.
With a swappable serlaizer the risks are higher however in theory even with this implementation if serialize/unserialize ever has a BC break in how it stores data (not expected) and one has multiple front ends that are operating on competing PHP versions this is going to have a significant amount flutter reverting back and forth with little to no knowledge or is occurring.
Sure this keeps the site online however at what cost? Is hiding a possibly significant system problem worth working in the rare case where this will occur ?
The core/rebuild.php script exists as a standalone (no container needed) method to deal with the cache system purge in the case that it is somehow compromised.