"A random commit I had checked out", which in this case evaluates to an old merge request https://repo.palemoon.org/martok/UXP-contrib/src/commit/438d4a8941cdd172e7960c694394ef43d8357e59. But it doesn't seem to be specific, I can also repro that with other things as well. For easier repro, I tried with a fresh checkout of ripgrep's own repo (master at f0faa91 as of now):

$ rg --version
ripgrep 14.1.1 (rev 4649aa9700)

features:+pcre2
simd(compile):+SSE2,-SSSE3,-AVX2
simd(runtime):+SSE2,+SSSE3,+AVX2

PCRE2 10.43 is available (JIT is available)

$ rg --json -F search | tail -n1 |jq
{
  "data": {
    "elapsed_total": {
      "human": "0.101663s",
      "nanos": 101662600,
      "secs": 0
    },
    "stats": {
      "bytes_printed": 3004406,
      "bytes_searched": 2947460,
      "elapsed": {
        "human": "0.044504s",
        "nanos": 44503600,
        "secs": 0
      },
      "matched_lines": 6966,
      "matches": 13611,
      "searches": 80,
      "searches_with_match": 80
    }
  },
  "type": "summary"
}

$ rg --stats -F search | tail -n8
13611 matches
6966 matched lines
80 files contained matches
218 files searched
1313732 bytes printed
4240475 bytes searched
0.041758 seconds spent searching
0.061247 seconds

"searches" and "searches_with_match" are the same where "searches" should be 218 here(?) and the "bytes_searched" are unclear to me.

Also, what are the status objects you refer to?

I got the terminology from the grep_printer man page wrong, the JSONL records should be called a "message", not an "object". So I should have said "status message", where we currently have only the final "summary message".

I'll look closer when I have hands on a keyboard.

What I meant is that I don't know what a status object or a status message is. I didn't mean to pick on minor terminology. I just don't know what you're referring to here. What do you want to be emitted that isn't? (Aside from the seeming incorrect summary statistics.)

Thanks!

What I mean is that we currently only have the begin/match/end messages for files that contain a match, but nothing at all to show overall progress. It would be nice to have some output on what the searcher is currently doing, even if it's just a counter for how many files have been whitelisted and searched.
I don't really read Rust, but the JSON printer seems to already support something like this via the always_begin_end option. That should make it so that every file opened is reported, not just the ones with matches.

OK, so apparently, the summary statistics for the JSON printer have been wrong... since the JSON printer was introduced? Kinda wild that nobody has reported that until now. I have a fix here: #3190

Wild. I guess really nobody uses the indicators, which also gives a lot of credit to your estimation below.

We could add a flag that lets users opt into it, but I am growing increasingly hesitant to add more flags to ripgrep because there are already so many.

I've expected that after reading a few other discussions here. Maybe turning --json from a switch into an option like --json=verbose might work, but that's not great either since most other output options don't work that way. A fork would be just as much if not more maintenance work, so I'll just go with parsing the --debug stream. Might even be faster on windows to consume two separate pipes since at least it won't need thread synchronization on the file descriptor as much.

Many thanks for all your work on this again!