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 of Asynchronous opetations status issue #29814

Merged

Conversation

nuzil
Copy link
Contributor

@nuzil nuzil commented Aug 31, 2020

Description (*)

Fix of Asynchronous opetations status issue. When using MYSQL Async queues. Caused by provided in 2.4 release new database field, which is not required to have for Mysql queues.

Fixed Issues (if relevant)

  1. Fixes Wrong handling some of asynchronous bulk operations and related mysql queue messages in Magento 2.4.0 #29718

Manual testing scenarios (*)

See Issue.

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)

nuzil and others added 3 commits July 3, 2020 09:48
for support B2B implementations
…g bulk operation with not set 'operation_id' during executing \Magento\Catalog\Model\Attribute\Backend\Consumer::process() method.
@m2-assistant
Copy link

m2-assistant bot commented Aug 31, 2020

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

⚠️ 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, 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

]
);
$this->bulkStatus = $this->objectManager->get(BulkStatus::class);
$catalogProductMock = $this->createMock(\Magento\Catalog\Helper\Product::class);
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @nuzil. What do you think about using imports everywhere instead of FQN? Currently, we use both. But I believe we may make the code a little bit more readable by using the same approach for all places.

Just a minor suggestion

@rogyar
Copy link
Contributor

rogyar commented Aug 31, 2020

@magento run all tests

@VladimirZaets
Copy link
Contributor

@magento I am working on it

@ghost
Copy link

ghost commented Aug 31, 2020

@m2-assistant[bot] unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

@VladimirZaets
Copy link
Contributor

@magento I am working on it

1 similar comment
@VladimirZaets
Copy link
Contributor

@magento I am working on it

@ghost
Copy link

ghost commented Aug 31, 2020

@m2-assistant[bot] unfortunately, only members of the maintainers team are allowed to assign developers to the pull request

@VladimirZaets
Copy link
Contributor

@magento I am working on it

@sidolov sidolov added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Aug 31, 2020
sidolov
sidolov previously approved these changes Aug 31, 2020
@nuzil
Copy link
Contributor Author

nuzil commented Sep 15, 2020

@engcom-Charlie
Looks like failed tests are not connected to PR

@magento-engcom-team
Copy link
Contributor

Hi @gabrieldagama, thank you for the review.
ENGCOM-8108 has been created to process this Pull Request
✳️ @gabrieldagama, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

  1. ✔️ Displayed messages like "1 item(s) have been successfully updated...".

Screenshot from 2020-09-21 13-54-31

  1. ✔️ Attribute values for related products updated.

  2. ✔️ New record(s) in the "queue_message" (related to the queues "product_action_attribute.update" and/or product_action_attribute.website.update) and new related record(s) in the "queue_message_status" table with status "4".

2020-09-21_13-58

  1. ✔️ No errors in system.log file

@m2-assistant
Copy link

m2-assistant bot commented Sep 23, 2020

Hi @nuzil, 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: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage Component: AsynchronousOperations Partner: Comwrap partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Wrong handling some of asynchronous bulk operations and related mysql queue messages in Magento 2.4.0
9 participants