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

Incorrect constructor of Magento\Sales\Model\Order\Address\Validator #21692

Closed
Bartlomiejsz opened this issue Mar 11, 2019 · 7 comments
Closed
Assignees
Labels
Component: Sales Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@Bartlomiejsz
Copy link
Contributor

Bartlomiejsz commented Mar 11, 2019

Summary (*)

Tested on 2.3, but exactly same logic is included in this constructor on 2.2-develop branch.
Constructor of Magento\Sales\Model\Order\Address\Validator includes logic and should not. The reason of it is that if this class is injected in constructor in Cli Command in some custom module, installation of Magento fails.

Examples (*)

  1. Add custom module with Cli Command in which Magento\Sales\Model\Order\Address\Validator is injected
  2. Try to install Magento from scratch using Cli.
  3. See following error: Base table or view not found: 1146 Table 'database.eav_entity_type' doesn't exist, query was: SELECT main_table.* FROM eav_entity_typeASmain_table"

Proposed solution

I'm preparing PR for this one.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 11, 2019
@magento-engcom-team
Copy link
Contributor

Hi @Bartlomiejsz. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@Bartlomiejsz do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Mar 12, 2019

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost ghost added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Component: Sales Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Mar 12, 2019
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Mar 12, 2019
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98657 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@MaksymGrom
Copy link

MaksymGrom commented Mar 22, 2019

@Bartlomiejsz Hello, CLI in Magento loads all Command classes and them injections
So you should use Proxy to avoid loading Repositories and other classes with the same problem
Please change your injection. (while issue is not resolved)
Magento\Sales\Model\Order\Address\Validator => Magento\Sales\Model\Order\Address\Validator\Proxy

Also, you can change the injection attribute via di.xml.
You can see this way in \Magento\Catalog\Console\Command\ImagesResizeCommand
magento/module-catalog/etc/di.xml:557

@Bartlomiejsz
Copy link
Contributor Author

@MaksymGrom you're right, it can be handled using proxy, but still such logic should not be included in constructor so I hope it will be merged soon.
Thank you for response!

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Mar 25, 2019
magento-engcom-team added a commit that referenced this issue Mar 25, 2019
…21693

 - Merge Pull Request #21693 from Bartlomiejsz/magento2:feature/fix_21692_incorrect_constructor
 - Merged commits:
   1. 28b047e
   2. b92ffa2
   3. fda4377
   4. b2004c3
   5. b86f981
   6. 73d88aa
magento-engcom-team added a commit that referenced this issue Mar 25, 2019
…21693

 - Merge Pull Request #21693 from Bartlomiejsz/magento2:feature/fix_21692_incorrect_constructor
 - Merged commits:
   1. 28b047e
   2. b92ffa2
   3. fda4377
   4. b2004c3
   5. b86f981
   6. 73d88aa
   7. 9c7fbfd
   8. e09429f
ihor-sviziev added a commit to Bartlomiejsz/magento2 that referenced this issue Mar 25, 2019
ihor-sviziev added a commit to Bartlomiejsz/magento2 that referenced this issue Mar 25, 2019
@magento-engcom-team
Copy link
Contributor

Hi @Bartlomiejsz. Thank you for your report.
The issue has been fixed in #21719 by @Bartlomiejsz in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.9 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Mar 29, 2019
magento-engcom-team added a commit that referenced this issue Mar 29, 2019
…validator #21719

 - Merge Pull Request #21719 from Bartlomiejsz/magento2:feature/backport_22_fix_21692_incorrect_constructor
 - Merged commits:
   1. 068eedf
   2. 8a4cfa4
   3. 43cc9a4
   4. f77f54d
   5. cece086
   6. 67b1d0a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Sales Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

3 participants