fees: prevent redundant estimates flushes #32748

pull ismaelsadeeq wants to merge 2 commits into bitcoin:master from ismaelsadeeq:06-2025-prevent-redundant-estimate-flushes changing 2 files +32 −5
  1. ismaelsadeeq commented at 5:53 am on June 14, 2025: member

    This PR does two things:

    1. It prevents redundant writes to the fee_estimates.dat file when there is no usable data available. For example, during IBD, blocks are still being connected, but unnecessary flushes still occur every hour.

    2. It updates the flushing log to use debug-level logging under the estimatefee category. It also ensures the log consistently includes only the file name, not the full path.

  2. DrahtBot commented at 5:53 am on June 14, 2025: contributor

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32748.

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

    Conflicts

    Reviewers, this pull request conflicts with the following ones:

    • #29641 (scripted-diff: Use LogInfo over LogPrintf [WIP, NOMERGE, DRAFT] by maflcko)
    • #29307 (util: explicitly close all AutoFiles that have been written by vasild)

    If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

  3. fees: prevent redundant estimates flushes 26c78d611d
  4. fees: make flushes log debug only
    - Also don't log the full file path, just the filename.
    48a3e8f577
  5. ismaelsadeeq force-pushed on Jun 14, 2025
  6. DrahtBot added the label CI failed on Jun 14, 2025
  7. DrahtBot commented at 6:05 am on June 14, 2025: contributor

    🚧 At least one of the CI tasks failed. Task fuzzer,address,undefined,integer, no depends: https://github.com/bitcoin/bitcoin/runs/44091090061 LLM reason (✨ experimental): The CI failure is caused by a thread-safety analysis error in policy_estimator.cpp due to unsafe mutex usage during a function call.

    Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

    • Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

    • A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

    • An intermittent issue.

    Leave a comment here, if you need help tracking down a confusing failure.

  8. DrahtBot removed the label CI failed on Jun 14, 2025

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-06-15 06:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me