fix(log): mark high totalBalanceChf FinancialDataLog entries of 2026-06-20 as invalid#3946
Merged
TaprootFreak merged 1 commit intoJun 20, 2026
Conversation
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
1 participant
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.
Recurrence of the daily transient totalBalanceChf spike (see #3884, #3889, #3892, #3903, #3916).
FinancialDataLog entries created on 2026-06-20 carry an implausibly high
totalBalanceChf(> 60 000 CHF) but were stampedvalid=true, becauseplusBalanceChfjumped ahead of the correspondingminusBalanceChfbooking and the deltas stayed withinfinanceLogTotalBalanceChangeLimit.totalBalanceChf > 60 000(same as 2026-06-18)FinancialDataLogonlydown()re-stampsvalid=truefor the same window/threshold (one-shot fix)