Skip to content

[bugfix] Update heimdall status correctly#1775

Merged
pratikspatil024 merged 1 commit intodevelopfrom
fix_heimdall_status
Sep 18, 2025
Merged

[bugfix] Update heimdall status correctly#1775
pratikspatil024 merged 1 commit intodevelopfrom
fix_heimdall_status

Conversation

@cffls
Copy link
Copy Markdown
Contributor

@cffls cffls commented Sep 18, 2025

Description

This commit fixes a bug where when heimdall is down, its status isn't correctly reflected in span store, resulting bor to continue sync/mine blocks. The fix will make FetchStatus and GetLatestSpan non-blocking, which would allow the status of heimdall to be properly updated in span store, and make waitUntilHeimdallIsSynced wait when heimdall is down.

Changes

  • Bugfix (non-breaking change that solves an issue)
  • Hotfix (change that solves an urgent issue, and requires immediate attention)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (change that is not backwards-compatible and/or changes current functionality)
  • Changes only for a subset of nodes

Testing

  • I have added unit tests
  • I have added tests to CI
  • I have tested this code manually on local environment
  • I have tested this code manually on remote devnet using express-cli
  • I have tested this code manually on amoy
  • I have created new e2e tests into express-cli

This commit fixes a bug where when heimdall is down, its status isn't correctly reflected in span store. The fix will make FetchStatus and GetLatestSpan non-blocking, which would allow the status of heimdall to be properly updated in span store.
@cffls cffls force-pushed the fix_heimdall_status branch from 5788c7a to 0f83b03 Compare September 18, 2025 00:27
@sonarqubecloud
Copy link
Copy Markdown

@pratikspatil024 pratikspatil024 merged commit 461b0dc into develop Sep 18, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants