add logs to upgrade flow to make it easier to triage errors #6589
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.
What does PR do? Any background context you want to provide?
I tried to upgrade within app and things were failing so I figured I can provide more information to myself during the upgrade process
What Issues does it Close? Any the relevant tickets?
N/A
Screenshots (if appropriate)
N/A
Where should the reviewer start?
the diff
How should this be manually tested?
tail -f
the logs and the run an upgrade. if things work, awesome. if they don't, you should have more information to point to why it doesn't work instead of a generic uncaught exception from phpQuestions:
Is there a related website / article to substantiate / explain this change?
Does the development wiki need an update?
Does the user documentation wiki need an update?
Does this add new dependencies?
Does this need to add new data to the demo database