Repository navigation
fix(debug): no false theme warnings at start-up; refresh rate logged once known - #1812
Merged
Merged
Conversation
… rate is logged once it is known
ZhuchkaTriplesix
force-pushed
the
fix/debug-log-noise
branch
from
October 25, 2026 12:50
c57c399 to
93ec4e4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two noisy lines of the debug console at every start (seen in a
flutter runlog):Querya theme: ignored editor_colors key "canvas"... andignored editor_colors workbench key "background"... for every key of a Querya theme.editor_colorsholds the editor and the workbench keys in one map; each of the two parsers reported the other's keys as ignored. Now only a key that neither reads is reported, once (unknown editor_colors key). Test added.Display refresh: 0.0 Hz: the line was printed at start-up, beforerefresh_rate2.x filledinfoasynchronously, so it always read 0. It is printed 2 s later, and as not reported by the platform when the rate is still unknown (Linux reports it per monitor through GDK, if at all).Debug-only output; no behaviour change. Not run locally (analyzer clean), CI will.