Added stacktrace to report error output when enabled #1634
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We have automated a Magento Contributor License Agreement verifier for contributions sent to our GitHub projects. |
|
@wsakaren Can you please rebase onto the current develop? It would also be nice if you would respond to the comments of @dkvashninbay . Also, the automated license agreement needs to be signed in order to process this PR further. Thanks! |
|
I don't have bandwidth at present to progress I'm afraid. Suggest close. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently just gives a description of error, no stack trace, which slows down debugging as you have to open in var/report. If reporting is set to trace mode IMO then it should also display the stack trace in browser.