Skip to content

fix(health): fix issue where chain id wasn't cached#98

Open
FranklinWaller wants to merge 1 commit intomainfrom
patch/broken-health-api
Open

fix(health): fix issue where chain id wasn't cached#98
FranklinWaller wants to merge 1 commit intomainfrom
patch/broken-health-api

Conversation

@FranklinWaller
Copy link
Copy Markdown
Member

Motivation

(Write your motivation here)

Explanation of Changes

(Write your explanation here)

Testing

(Write your test plan here)

Related PRs and Issues

(Link your related PRs and Issues here)

@Thomasvdam
Copy link
Copy Markdown
Member

I'm not sure if this entirely correct, because now the health check doesn't actually verify that the proxy can reach the chain in future health checks. Maybe wrap it in a cache with TTL until we have time to properly think of how to do a health check mechanism that harmonises core and Fast?

@FranklinWaller FranklinWaller force-pushed the patch/broken-health-api branch from aa88d20 to 48cdfbb Compare March 25, 2026 17:30
@FranklinWaller
Copy link
Copy Markdown
Member Author

@Thomasvdam I changed it to do without caching because we do indeed want to know which proxies are unhealthy. Instead i've opted for just the fastOnly flag. Then the health endpoint won't return a unhealthy status when the chain is upgrading.

@FranklinWaller
Copy link
Copy Markdown
Member Author

Also made the better effect version, this is just a hotfix

#100

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