-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
No surprises in production mode #7659
Comments
Integrity test That said, this check should be removed. |
@antonkril great to hear that this is being improved. Just to provide some more context around this. The main problem is that the compiler with the above check applied is not run in developer mode and you can end up with something like this: 1.) Install the following extension https://github.com/fooman/CompilerProdVsDev with 2.) "Test" the extension by opening http://example.com/foomancompilerprodvsdev/example 3.) Run Actual Result
This leaves the store offline as it is still in maintenance mode and in a semi compiled state. This is particularly bad for any one installing through the Web Setup Wizard as they don't have any means of recovery without resorting to command line. |
Hi @fooman On |
@shiftedreality tested with 2d6bb43 and I am getting
which is much better as it doesn't take the store down. The above error message was repeated quite a few times when 1 would have been sufficient. |
Hello @fooman, we couldn't reproduce the issue on 2.0.13 and 2.1.5. If there is still the issue, please provide additional info and specific version. |
Still an issue in Magento CE 2.1.5 Our Magento is installed via composer but the Magenest_QuickBooksDesktop module is committed to our repository. When we do a deploy to the remote server this is the error we get during the
|
Cross reference to PR #8955 |
hi @fooman, the issue is reproducible, the internal ticket is created MAGETWO-66539. |
closing this issue as PR #8955 which addresses this problem merged into mainline |
|
Preconditions
Steps to reproduce
bin/magento setup:di:compile
Expected result
Actual result
This is problematic as it is unexpected. As a developer I would expect the developer mode to scream at me with any issue that I might face in production mode. Any error that is not coming up in developer mode but only appears in production mode creates the real potential of code tripping up sites that are live sites.
The text was updated successfully, but these errors were encountered: