Skip to content

Remove hack in chain_head_listener #5240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

leoyvens
Copy link
Collaborator

This was added in a time when we were having problems with receiving chain head updates and were trying workarounds. This one had a hypothesis of a deadlock in tokio Watch::send. I was never able to corroborate this, no other tokio user ever reported something like this and improvements have since been made to the internals of Watch. So there isn't much justification for keeping this hack.

This was added in a time when we were having problems with
receiving chain head updates and were trying workarounds.
This one had a hypothesis of a deadlock in tokio Watch::send.
I was never able to corroborate this, no other tokio user ever
reported something like this and improvements have since been
made to the internals of `Watch`. So there isn't much justification
for keeping this hack.
@leoyvens
Copy link
Collaborator Author

I tried this on a canary build in studio and it resolved some of the no chain head update for 30 seconds, polling for update logs, which is a great result.

@fordN fordN requested a review from mangas February 26, 2024 16:55
@leoyvens leoyvens merged commit 3418dc1 into master Mar 1, 2024
@lutter lutter deleted the leo/remove-chain-head-listener-hack branch April 17, 2025 18:45
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.

2 participants