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 caching Magento Metadata getVersion #26001

Merged
merged 3 commits into from
Dec 18, 2019

Conversation

luklewluk
Copy link
Contributor

@luklewluk luklewluk commented Dec 11, 2019

Fix caching result in ProductMetadata::getVersion.

Description (*)

My change fixes issue that getVersion result never gets cached.

Original Pull Request: #24030
Caching was broken by this commit: 37f6f6a

In order to fix the issue, we should put that line where it was originally.

Fixed Issues (if relevant)

  1. Slow Performance of ProductMetadata::getVersion #24025: Slow Performance of ProductMetadata::getVersion

Manual testing scenarios (*)

  1. have a module installed that relies on the product version to determine e.g. feature compatibility
  2. profile uncached requests

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)
  • All automated tests passed successfully (all builds are green)

@luklewluk luklewluk requested a review from buskamuza as a code owner December 11, 2019 21:42
@m2-assistant
Copy link

m2-assistant bot commented Dec 11, 2019

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

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

beberlei referenced this pull request Dec 11, 2019
- fix merge conflicts and update lock file
@kalpmehta kalpmehta self-assigned this Dec 12, 2019
@kalpmehta
Copy link
Contributor

Hi @luklewluk, thanks for your contribution! Please sign the Adobe CLA so we can process this PR.

@luklewluk luklewluk closed this Dec 12, 2019
@m2-assistant
Copy link

m2-assistant bot commented Dec 12, 2019

Hi @luklewluk, 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.

@luklewluk luklewluk reopened this Dec 12, 2019
@ghost ghost unassigned kalpmehta Dec 12, 2019
@ihor-sviziev ihor-sviziev self-assigned this Dec 13, 2019
Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

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

Hi @luklewluk,
Thank you for contribution! As for me - your changes looks good.

As as part of #24030 changes weren't covered with unit tests - we got regression very soon. In order to prevent such situation in future - could you cover these changes with unit test?

Also please review failing tests and adjust your code / tests to make them pass.

@luklewluk
Copy link
Contributor Author

Hi @ihor-sviziev
I have added unit tests and modified the class description so it passed Static Tests. Please check if it's okay now.
Thanks!

@ihor-sviziev ihor-sviziev added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage labels Dec 13, 2019
@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

@luklewluk thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@engcom-Charlie
Copy link
Contributor

✔️ QA Passed

@m2-assistant
Copy link

m2-assistant bot commented Dec 18, 2019

Hi @luklewluk, 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.

@erikhansen
Copy link
Contributor

For the record, turning this PR into a patch and applying it to 2.3.3 resolved this issue for me. More details here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants