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
M 2.4.0 upgrading issue - Unable to apply patch Magento\Review\Setup\Patch\Schema\AddUniqueConstraintToReviewEntitySummary #29352
Comments
Hi @jesperbrejning. Thank you for your report.
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:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 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 |
Hmm, that's interesting, the regex you refer to is I think you have a point here, the problem is inside the
to:
or:
Could you test both these suggested regexes and let me know which ones fixes your issue? For completeness sake, can you specify the PHP version and the version of the pcre library you are using.
Thanks! |
I can very easily reproduce the problem using PHP 7.3 and 7.4 (it works on PHP 7.2) with:
I'm using:
This most likely happens because PHP 7.3 and 7.4 upgraded from the pcre library version 1 to version 2 and the last one is probably more stricter: https://php.watch/versions/7.3#pcre2 Thanks for the bug report, it's truly an important bug and hopefully somebody will fix this shortly (and search the entire codebase for other possible variants of this bug and also fix those) |
Can confirm I see this bug with a 2.4. upgrade
|
To amend my other comment, I couldn't replicate this using vanilla Magento installs from 2.3.4 to 2.4.0 (the above case was 2.3.4 to 2.4.0) so its not clear why its failing to update in our case. |
Hello @jesperbrejning, @hostep, @martysmojo |
Hi @jesperbrejning. Thank you for your report and collaboration! The issue was fixed by Magento team. The fix was delivered into The fix will be available with the upcoming |
Preconditions
Install Magento 2.3.5 CE using composer
Steps to reproduce
Please find more details here [https://github.com//issues/29352>
The text was updated successfully, but these errors were encountered: