String as a key used, might be damaged accidentally.

[iaroslavglodov]

magento2/app/code/Magento/Quote/Model/Quote/Address.php

Line 679 in 32ed03c

$this->setData('cached_items_all', $items);

Summary (*)

String key 'cached_items_all' MUST be changed to $key, or even better with the predefined class constant CACHE_KEY_ITEMS_ALL.

[m2-assistant]

Hi @iaroslavglodov. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ejaz-alam]

@magento I am working on this

[magento-engcom-team]

Hi @iaroslavglodov. Thank you for your report.
The issue has been fixed in #30579 by @ejaz-alam in 2.4-develop branch
Related commit(s):

• 6970b19c234d752d2f4137580c877b37d96f77d5
• fd4a5a7cb63e2c712e03de61b820f92a47a33a2e

The fix will be available with the upcoming 2.4.2 release.