-
Notifications
You must be signed in to change notification settings - Fork 143
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
[Themes] Add debug logging for theme fetch errors #5203
[Themes] Add debug logging for theme fetch errors #5203
Conversation
Coverage report
Show files with reduced coverage 🔻
Test suite run success2007 tests passing in 906 suites. Report generated by 🧪jest coverage report action from 25f9861 |
We detected some changes at packages/*/src and there are no updates in the .changeset. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @jamesmengo!
I had the same internal debate about this. My initial thought was that the command with the request ID would be enough to provide us some context. However, I don't think this line is harmful :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm +1 for adding this in. Adding a one liner to debug logs wouldn't be too noisy imo.
…theme_errorhandler [Themes] Add debug logging for theme fetch errors
WHY are these changes introduced?
Adds debug logging to report that themeFetch failed on top of the changes introduced in #5200
This is likely inconsequential, but may come in handy for debugging something in the future (even more so because the client will handle failures silently otherwise)
@karreiro Do we want to do this? Would we be adding too much noise?