You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Checks completing flicker when they are really fast #113
Currently, scope run shows a tree of all the checks as they run, but then hides them when complete. I think for an end-user, it can be a little disorienting to see them pop up quickly, and then go away.
I'm wondering if we could do one of:
keep the check there, with info about it finishing successfully, how long it took, etc
keep the check there for at least a few seconds so it's not like an immediately flash
Evaluated as part of an issue-validity review (2026-07-28). Closing as not planned.
Technically this still reproduces: the tree UI is driven by tracing-indicatif spans (src/doctor/runner.rs:433-506) that disappear the instant they close, with no completion state, elapsed-time display, or minimum-visibility duration. That's been true since the progress bar was introduced in PR #84 (March 2024), and nothing since (including the recent span-nesting change in #346) has touched this.
That said, this flicker is largely an inherent tradeoff of a fast, spinner/tree-style progress UI rather than a defect — and --progress plain avoids it entirely by not using the animated tree renderer at all. That's already our team's more common way of running scope doctor internally. Given the workaround exists and the fancy-mode flicker is expected behavior for that UI style, we're not planning to invest in a completion/hold-duration fix here. Happy to reopen if the fancy-progress mode becomes the primary path and this becomes more of a pain point.
Activity
rubberduck203 commentedon Jul 28, 2026
Evaluated as part of an issue-validity review (2026-07-28). Closing as not planned.
Technically this still reproduces: the tree UI is driven by
tracing-indicatifspans (src/doctor/runner.rs:433-506) that disappear the instant they close, with no completion state, elapsed-time display, or minimum-visibility duration. That's been true since the progress bar was introduced in PR #84 (March 2024), and nothing since (including the recent span-nesting change in #346) has touched this.That said, this flicker is largely an inherent tradeoff of a fast, spinner/tree-style progress UI rather than a defect — and
--progress plainavoids it entirely by not using the animated tree renderer at all. That's already our team's more common way of runningscope doctorinternally. Given the workaround exists and the fancy-mode flicker is expected behavior for that UI style, we're not planning to invest in a completion/hold-duration fix here. Happy to reopen if the fancy-progress mode becomes the primary path and this becomes more of a pain point.