Summary
QfcHomeController.WriteMetricsAsync enqueues QuickFiler session metrics into a BlockingCollection<string> that no consumer ever drains, so the metrics are never written to disk. The consumer guard can never pass and the consumer timer is never started.
Environment
- OS/version: Windows 11 Pro 10.0.26200
- Python version: n/a (C# / .NET Framework 4.8 VSTO add-in)
- Command/flags used: QuickFiler launched from the TaskMaster ribbon; any session that completes and writes metrics
- Data source or fixture: Live Outlook mailbox
Steps to Reproduce
- Launch QuickFiler and file at least one batch of messages so a metrics line is produced.
- Complete the session so
WriteMetricsAsync runs.
- Inspect the configured session metrics file (
Globals.FS.Filenames.EmailSession).
Expected Behavior
The session metrics line is appended to the configured metrics file.
Actual Behavior
No metrics line is written. The line is added to the in-memory _metrics collection and remains there until the process exits.
Logs / Screenshots
Impact / Severity
Medium: no user-visible functional regression in filing, but the QuickFiler performance-metrics feature produces no output at all, so the data intended to drive tuning does not exist.
Source
From: docs/features/potential/2026-08-07-qfc-home-controller-metrics-never-flushed.md
Summary
QfcHomeController.WriteMetricsAsyncenqueues QuickFiler session metrics into aBlockingCollection<string>that no consumer ever drains, so the metrics are never written to disk. The consumer guard can never pass and the consumer timer is never started.Environment
Steps to Reproduce
WriteMetricsAsyncruns.Globals.FS.Filenames.EmailSession).Expected Behavior
The session metrics line is appended to the configured metrics file.
Actual Behavior
No metrics line is written. The line is added to the in-memory
_metricscollection and remains there until the process exits.Logs / Screenshots
Impact / Severity
Medium: no user-visible functional regression in filing, but the QuickFiler performance-metrics feature produces no output at all, so the data intended to drive tuning does not exist.
Source
From: docs/features/potential/2026-08-07-qfc-home-controller-metrics-never-flushed.md