Skip to content

Simplify version constraint for the php-amqplib/php-amqplib package, … #28585

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

Closed
wants to merge 1 commit into from

Conversation

hostep
Copy link
Contributor

@hostep hostep commented Jun 5, 2020

…now that the php extension sockets is considered required for Magento.

Description (*)

As requested in #27200 by @melnikovi, here's a pull request which simplifies the version constraint on the php-amqplib/php-amqplib package now that the php extension sockets is considered required for Magento 2.

Version 2.7 of php-amqplib/php-amqplib didn't require the sockets extension, but since version 2.8.1 it became required.

This prevents developers from accidentally updating the composer.lock file inside this github repo as well as inside projects where it changes the version of php-amqplib/php-amqplib based on if they have the sockets extension installed or not, which can be quite annoying to deal with.

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Dependency php-amqplib/php-amqplib vs php extension sockets causes inconsistent composer.lock file #27200

Manual testing scenarios (*)

  1. Have a PHP installation where the sockets extension is not installed
  2. Try to install Magento using composer after this fix, it should no longer work.

Questions or comments

I'm not entirely sure, but should we also define ext-sockets in the composer.json file of Magento 2? I'm a bit confused about the comment from @dobooth if the list of extensions in devdocs is solely generated from the composer.json file, or from all composer dependencies?

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

…now that the php extension sockets is considered required for Magento.
@m2-assistant
Copy link

m2-assistant bot commented Jun 5, 2020

Hi @hostep. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@hostep
Copy link
Contributor Author

hostep commented Jun 5, 2020

Not really needed to run any tests here I believe, since the composer.lock file contains no real changes, so no dependencies are being changed here.

@ihor-sviziev ihor-sviziev self-assigned this Jun 5, 2020
@ihor-sviziev ihor-sviziev added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Jun 5, 2020
@ghost ghost added the Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. label Jun 5, 2020
ihor-sviziev
ihor-sviziev previously approved these changes Jun 5, 2020
@ihor-sviziev
Copy link
Contributor

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-7626 has been created to process this Pull Request

@ihor-sviziev
Copy link
Contributor

@hostep i think we don’t need to add dependency to sockets extension as magento actually not depends on it directly, only through library

@chernenm-zz chernenm-zz added the Severity: S1 Affects critical data or functionality and forces users to employ a workaround. label Jun 11, 2020
@sdzhepa sdzhepa added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Triage: Done Has been reviewed and prioritized during Triage with Product Managers and removed Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Jun 11, 2020
@lenaorobei
Copy link
Contributor

Commit was cherry-picked and merge to 2.4.0 is in progress.

Copy link
Contributor

@engcom-Alfa engcom-Alfa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @hostep. Could you resolve merge conflicts?

@ghost ghost dismissed ihor-sviziev’s stale review June 16, 2020 07:17

Pull Request state was updated. Re-review required.

@hostep
Copy link
Contributor Author

hostep commented Jun 16, 2020

@engcom-Alfa: since @lenaorobei already merged this in the release branch for 2.4.0, there is no need anymore for this PR, right? We can probably close it?

@lenaorobei
Copy link
Contributor

@hostep thanks for this contribution! Yes, it was delivered to 2.4.0.

@lenaorobei lenaorobei closed this Jun 16, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jun 16, 2020

Hi @hostep, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: needs update Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround. Triage: Done Has been reviewed and prioritized during Triage with Product Managers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dependency php-amqplib/php-amqplib vs php extension sockets causes inconsistent composer.lock file
7 participants