Open sgeleon opened 1 week ago
Hi @sgeleon. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
@sgeleon: please edit your post and remove the repositories
section, because it's full of passwords you probably don't want to leak to the outside...
As for the issue you are having, if I have to guess, it might be related to yireo/magento2-replace-inventory
...
But you should seek help elsewhere, this is a project specific problem, this doesn't seem to be an issue in core Magento code, as many people already have upgraded to 2.4.7-p1 without this error.
Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Hi @hostep
@sgeleon: please edit your post and remove the repositories section, because it's full of passwords you probably don't want to leak to the outside...
Thank you for your attention.
As for the issue you are having, if I have to guess, it might be related to yireo/magento2-replace-inventory... But you should seek help elsewhere, this is a project specific problem, this doesn't seem to be an issue in core Magento code, as many people already have upgraded to 2.4.7-p1 without this error.
I fixed it by change version of magento in composer.js and execute: composer update
This bug reproduce then you try update by:
composer require magento/product-community-edition 2.4.7-p1 -W
@sgeleon
Per Magento Docs the command required for update is:
composer require-commerce magento/product-community-edition 2.4.7-p1 --no-update
and not
composer require magento/product-community-edition 2.4.7-p1 -W
Perhaps that would also fix your error.
Hi @sgeleon
Thanks for reporting and collaboration.
Verified the issue on Magento 2.4.7-p1 after upgrading the instance from Magento 2.4.7.
We can upgrade the instance from 2.4.7 to 2.4.7-p1 successfully
Please take a look at the screenshots I've attached. Let us know if we missed anything.
After upgrading the instance from 2.4.7 to 2.4.6-p1
After performing bin/magento setup: upgrade
Preconditions and environment
Updating from version 2.4.7 to 2.4.7-p1
My composer file:
Steps to reproduce
1) Update by composer using the next command:
2) Execute bin/magento se:up 3) Get error
Expected result
Get nothing in command line after execute step 2.
Actual result
Error
Additional information
No response
Release note
No response
Triage and priority