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

Reprocess PR 39097 fixes requireJS mixins racecondition with require calls in dom #39691

Open
wants to merge 8 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

ioweb-gr
Copy link
Contributor

@ioweb-gr ioweb-gr commented Mar 1, 2025

Description (*)

This is an attempt to reprocess the race condition issue with mixins not loading from PR #39097 because it has been stale for very long waiting to be merged with the 2.4-develop branch. I resolved all merge conflicts and here is the new one. Hopefully this will work the same as I noticed on 2.4.-develop a lot of require.js changes were included.

Related Pull Requests

#39097

Fixed Issues (if relevant)

  1. Check fixes requireJS mixins racecondition with require calls in dom #39097

Manual testing scenarios (*)

  1. ...
  2. ...

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)

Copy link

m2-assistant bot commented Mar 1, 2025

Hi @ioweb-gr. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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 Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@ioweb-gr ioweb-gr changed the title Reprocess PR 39097 Reprocess PR 39097 fixes requireJS mixins racecondition with require calls in dom Mar 1, 2025
@Den4ik Den4ik self-requested a review March 3, 2025 08:37
@engcom-Hotel engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Mar 4, 2025
@Den4ik
Copy link
Contributor

Den4ik commented Mar 5, 2025

@magento run all tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants