Skip to content
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

Fix Passing null to parameter #1 ($string) of type string #35441

Conversation

nazarklovanych
Copy link

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes [Magento 2.4.4] MQ consumers run into issue "Deprecated Functionality: trim() .. magento/framework-amqp/Config.php on line 143" on PHP 8.1 #35380

Manual testing scenarios (*)

Install fresh (vanilla) Magento instance
1.1 composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition
1.2 run install with AMQP: e.g. bin/magento setup:install --base-url="http://magento-ce.test/" --base-url-secure="https://magento-ce.test/" --use-secure-admin=1 --use-rewrites=1 --use-secure=1 --db-host="127.0.0.1" --db-name=magento_ce --db-user=root --db-password=root --backend-frontname=admin --admin-firstname=admin --admin-lastname=admin --admin-email=admin@magento-ce.test --admin-user=admin --admin-password=admin123 --language=en_US --currency=EUR --timezone=Europe/Berlin --amqp-host=localhost --amqp-port=5672 --amqp-user=admin --amqp-password=admin --amqp-virtualhost=magento_ce --elasticsearch-host=localhost --elasticsearch-port=9207 --session-save=redis --session-save-redis-host=localhost --session-save-redis-port=6379 --session-save-redis-db=0 --cache-backend=redis --cache-backend-redis-server=localhost --cache-backend-redis-port=6379 --cache-backend-redis-db=1 --page-cache=redis --page-cache-redis-server=localhost --page-cache-redis-port=6379 --page-cache-redis-db=2 --cleanup-database
Start MQ consumer like: bin/magento queue:consumer:start async.operations.all

Questions or comments

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)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented May 6, 2022

Hi @nazarklovanych. Thank you for your contribution
Here are 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
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label May 6, 2022
@nazarklovanych
Copy link
Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@karyna-t
Copy link
Contributor

Hello @nazarklovanych
Could you please fix failed static tests?
Thank you in advance.

@nazarklovanych
Copy link
Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@nuzil
Copy link
Contributor

nuzil commented May 13, 2022

Great stuff! Thanks :-)

@ishakhsuvarov
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@glo71317
Copy link
Contributor

@magento run Functional Tests CE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@glo71317
Copy link
Contributor

@magento run Functional Tests CE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Charlie engcom-Charlie self-assigned this Jun 7, 2022
@engcom-Charlie
Copy link
Contributor

Hi @engcom-Alfa,

I have merged latest 2.4-develop into this PR branch and resolved all the conflicts.

You can proceed with testing.

Thank you!

@engcom-Alfa
Copy link
Contributor

@magento run all test

@magento-automated-testing
Copy link

Failed to run the builds. Please try to re-run them later.

@engcom-Alfa
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Alfa
Copy link
Contributor

engcom-Alfa commented Jun 20, 2022

✔️ QA Passed

Executed with the steps as shown in above-comment.

Before: ✖️ We were getting an error as mentioned in the same above-comment.

After: ✔️ Consumer able start command execution without any errors!

No additional regression testing required to be added since it is relevant to the command failure fix with particular PHP version.

@engcom-Alfa
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Alfa
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Alfa
Copy link
Contributor

Even after multiple tried "Functional Tests EE" job is getting failed! Hence moving the PR to Extended Testing.

@engcom-Charlie
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Charlie
Copy link
Contributor

As the build is successful now, moving this PR to Merge in Progress.

Thank you!

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept
Projects
None yet
10 participants