-
-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symfony recipe update conflict resolution fails with phpstorm #1362
Comments
I can confirm this. It did happen only on @Tib-z Did it happen on all recipes or just the first one? |
As far as I remember for me it happend with doctrine/doctrine-bundle and symfony/twig-bundle (not with the first one update). |
Flex is doing something weird and / or out of spec with the actual git repository itself during updates that's throwing phpstorm off. |
Ooooh I'm so glad I'm not alone on this. |
When using PhpStorm v2024.*, running certain Symfony Flex recipe updates (e.g., composer recipes:update doctrine/doctrine-bundle) causes conflict resolution to fail. The following error is displayed in PhpStorm:
A bug report has already been submitted to the JetBrains issue tracker (IJPL-158448). However according to JetBrains staff, the error is triggered by a missing blob, potentially linked to the Symfony recipe repository or the update process itself.
I haven't investigated Symfony Flex internals or debugged the issue deeply, so I cannot determine whether this is a problem with Symfony Flex's handling of files during recipe updates or a bug in PhpStorm.
Steps to Reproduce (also refer to the jetbrains ticket for repro):
Expected Behavior:
Conflict resolution should work seamlessly after recipe updates without errors.
Actual Behavior:
Conflict resolution fails, displaying an error about being unable to read an object or file.
The text was updated successfully, but these errors were encountered: