-
Notifications
You must be signed in to change notification settings - Fork 178
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
feature_request(debug): detailed debug information #63
Comments
I've opened BurntSushi/ripgrep#1610 to solve outputting more info about preprocessors via the I've also added lots of debug statements and timings in 7b70188, here's an example output of next version (very complex example, usually you don't have an archive that deep):
|
Type: Question ❓ 1. New releaseIs any information, when roughly will the next version of ripgrep-all was released? ripgrep-all has new features, but the latest release was released almost 2 months ago. I wait, when I can review new ripgrep-all features. 2. TipChocolatey supports pre-releases, if developers is not ready to release a stable version. Thanks. |
@phiresky , is now there any rough information on when the new version be released? Thanks for the great tool. |
I think this is fixed in 1.0.0-alpha.4 edit: also 0.10 |
1. Summary
It would be nice, if debug information will be more detailed.
Below I wrote features that would be nice to see in debug logs.
2. Debugging features
3. Argumentation
3.1. Information for each file
It would be nice if the processing information for each file will be in output.
This will allow users to quickly determine:
3.1.1. Example
and so on.
3.2. Time
It would be nice get the time spent processing each file. Users will be able to check slow adapters and then switch to another adapter command or replace adapter (after #60 implemented).
3.2.1. Example
Minutes and seconds in the output. For example:
0:14
— 14 seconds,1:7
— 1 minute, 7 seconds.3.3. Cache
It would be nice to show, whether the cache was used when processing specific file. This information required to determine, why ripgrep-all have a slow speed for some files.
3.3.1. Example
Cache: true
, if cache used for file processing;Cache: false
, if no.4. Example of expected behavior
4.1. Data
For example, I have a directory with files
KiraFirst.epub
,KiraSecond.rtf
,KiraThird.djvu
,KiraFourth.doc
andKiraFifth.pdf
. I run commandrga "Kira Goddess!"
in this directory.4.2. Behavior
Thanks.
The text was updated successfully, but these errors were encountered: