ISSUE-39053 Move publish() call outside of open DB transaction, fix for operations to exists in DB before scheduling bulk

[pczerkas]

Related Pull Requests

https://github.com/magento/magento2/commit/d096342f0d259e3bfca66d6d6c4ca3caef858a3b

Fixed Issues (if relevant)

1. Fixes magento/magento2#39053

[m2-assistant[bot]]

Hi @pczerkas. Thank you for your contribution! Here are some useful tips on 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

:exclamation: 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 :information_source: Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation. Join Magento Community Engineering Slack and ask your questions in #github channel.

[pczerkas]

@magento run all tests

[93kamikaze]

@magento run all tests

[pczerkas]

@magento run all tests

[pczerkas]

@magento run all tests

[pczerkas]

@magento run all tests

[pczerkas]

@magento need review

[pczerkas]

@magento run all tests

[pczerkas]

@magento run all tests