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
Add debug information to cache results #1015
Add debug information to cache results #1015
Conversation
…on-to-cache-results
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #1015 +/- ##
============================================
+ Coverage 89.10% 89.26% +0.15%
- Complexity 1160 1179 +19
============================================
Files 107 109 +2
Lines 2956 3027 +71
============================================
+ Hits 2634 2702 +68
- Misses 322 325 +3
☔ View full report in Codecov by Sentry. |
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.
Nice!
Type: feature
Issue: -
Breaking change: no
Addendum to #1011
I found the lack information of the cache difficult to debug. There's no information presented regarding if the cache is used, which it is read from, or if the cache is still valid. I added a few cli flags to show more information:
Feature
-v, -vv, -vvv
. Which increments the verbosity of the output. Default is 'Normal'.-v
,-vv
, or-vvv
is specified, the behaviour is currently as it is now and nothing is printed.Changes
OutputInterface
based on Symfony's Console package. Should be drop-in replacement if at some point Symfony Console can/will be used.NullOutput
(for tests) andStreamOutput
classes to be able to write output with verbosity level.Quiet
,Normal
(default),Verbose
,VeryVerbose
andDebug
. Currently onlyVeryVerbose
andDebug
is being written to.Note, this branch contains the changes from PR 1011. I don't seem to be able to target that PR in this PR.