pub struct AnalysisReport {
pub candidates: u64,
pub bytes_read: u64,
pub elapsed_ns: u64,
pub applied: u64,
pub stale: u64,
pub lines: AnalyzerCoverage,
pub code: Option<AnalyzerCoverage>,
pub words: Option<AnalyzerCoverage>,
}Expand description
Operational counters from one content-analysis pass.
Fields§
§candidates: u64Regular files considered by the requested profile.
bytes_read: u64Bytes actually returned by fresh file reads, including partial binary probes.
elapsed_ns: u64Wall time spent processing fresh candidates.
applied: u64Results accepted by the index’s conditional mutation boundary.
stale: u64Results discarded because indexed metadata changed while workers ran.
lines: AnalyzerCoverageCoverage of the shared lines unit.
code: Option<AnalyzerCoverage>Coverage of the code unit when requested.
words: Option<AnalyzerCoverage>Coverage of the words unit when requested.
Implementations§
Source§impl AnalysisReport
impl AnalysisReport
Sourcepub fn is_complete(&self) -> bool
pub fn is_complete(&self) -> bool
Whether content analysis completed without an operational failure.
Binary data, invalid UTF-8, and unsupported analyzers are coverage outcomes. They remain visible in roll-ups but do not mean the filesystem operation failed.
Sourcepub fn failure_message(&self) -> Option<String>
pub fn failure_message(&self) -> Option<String>
Explain operational failures without presenting expected coverage as an error.