chore: skip fee estimate example#1695
Merged
Merged
Conversation
Signed-off-by: dosi <dosi.kolev@limechain.tech>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Up to standards ✅🟢 Issues
|
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
SimiHunjan
approved these changes
May 8, 2026
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.
Description:
Skip the
fee_estimate_queryexample in therun-examplesTask so a freshlocal mirror node doesn't fail the run.
fee_estimate_queryto the skip list inTaskfile.ymlwith a commentexplaining the mirror-node-sync flake
Notes for reviewer:
The example itself works against a steady-state network — the failure mode is
specifically that a freshly-started local mirror node hasn't ingested the
operator's state when
run-examplesinvokes it back-to-back with all theothers.
Related issue(s):
Fixes #
Notes for reviewer:
Checklist