Changed repository name of one of the composer.lock included packages.

[miloszowi]

In the composer.lock file in current Magento 2 codebase we can find module named allure-framework/allure-php-api which has source on <https://github.com/allure-framework/allure-php-commons.git>

According to this commit repository name has been changed leading to crash every Magento 2 application failing caused by not existing source.

 

  - Installing allure-framework/allure-php-api (1.1.8): Downloading (connecting...).................Downloading (0%) ............ Failed to download allure-framework/allure-php-api from dist: The "https://codeload.github.com/allure-framework/allure-php-commons/legacy.zip/<hash>" file could not be downloaded (HTTP/1.1 404 Not Found) Now trying to download from source - Installing allure-framework/allure-php-api (1.1.8): Failed to update https://github.com/allure-framework/allure-php-commons.git in cache, package installation for allure-framework/allure-php-api might fail. Cloning <hash> from cache <hash> is gone (history was rewritten?)

[m2-assistant]

Hi @miloszowi. 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

[andrewbess]

Hello @miloszowi
Thank you for your report.
Yes, the problem is actual now.

For fast fix of it you can update this composer dependency using cli-command composer update allure-framework/allure-php-api.

[miloszowi]

Treat this thread as an info, as I already resolved the issue.

Making such a change without any warning before is not acceptable and should be avoided.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[m2-assistant]

Hi @andrewbess. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[rayat]

Hi Guys, a quick fix if you are stuck on DevOps composer install:

allure-framework/allure-php-api#76 (comment)

[ihor-sviziev]

Also, here is clarification what's happened with repo allure-framework/allure-php-api#76 (comment)

[ra-cricut]

Hi Guys, a quick fix if you are stuck on DevOps composer install:

allure-framework/allure-php-api#76 (comment)

@rayat flushing composer cache prior running the following command should make proper updates on the composer.lock file: composer update allure-framework/allure-php-api

[m2-assistant]

Hi @ihor-sviziev. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[ihor-sviziev]

Hi @miloszowi,
The internal team already fixed this issue in the 2.4-develop branch in 2670c4b.

For those who experience this issue on their projects - please run the following command:

composer update allure-framework/allure-php-api

If you wonder what's happened with the allure-framework/allure-php-api repository - you can reed it here: allure-framework/allure-php-api#76 (comment)

I'm closing this issue.