Why doctrine failed to save the key? #7444

Closed
opened 2026-01-22 15:51:46 +01:00 by admin · 1 comment
Owner

Originally created by @profesionalaiesam on GitHub (Nov 29, 2024).

Bug Report

Q A
Version 2.16.2
Previous Version if the bug is a regression x.y.z

Summary

Why do you think it happens? Sometimes in prod it just doesn't save the key correctly.

Current behavior

image

Expected behavior

How to reproduce

I don't know how to reproduce this

Originally created by @profesionalaiesam on GitHub (Nov 29, 2024). ### Bug Report <!-- Fill in the relevant information below to help triage your issue. --> | Q | A |-------------------------------------------- | ------ | Version | 2.16.2 | Previous Version if the bug is a regression | x.y.z #### Summary Why do you think it happens? Sometimes in prod it just doesn't save the key correctly. #### Current behavior ![image](https://github.com/user-attachments/assets/0c2e9ec0-97b3-4618-8058-07f500fb046a) #### Expected behavior #### How to reproduce I don't know how to reproduce this
admin closed this issue 2026-01-22 15:51:47 +01:00
Author
Owner

@greg0ire commented on GitHub (Nov 29, 2024):

With the details you've provided, all I can say is this looks like a symfony/cache problem. Also, you should update your packages before you file bug reports, 2.16.x is no longer supported.

@greg0ire commented on GitHub (Nov 29, 2024): With the details you've provided, all I can say is this looks like a `symfony/cache` problem. Also, you should update your packages before you file bug reports, 2.16.x is no longer supported.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#7444