Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Restore SyncIncomingBlocks listening in Chainwatch #51

Closed
placer14 opened this issue Aug 31, 2020 · 0 comments · Fixed by filecoin-project/lotus#3442
Closed

Restore SyncIncomingBlocks listening in Chainwatch #51

placer14 opened this issue Aug 31, 2020 · 0 comments · Fixed by filecoin-project/lotus#3442
Labels
kind/bug Something isn't working

Comments

@placer14
Copy link
Contributor

Chainwatch needs to be capturing incoming blocks so we can identify reorg detectable by a node. While Sentinel treats this as a Telegraf concern, there are still users which are consuming this data from Chainwatch. This will make sure it continues to be there until we can properly support a freshly deployed Sentinel.
@placer14 placer14 added the kind/bug Something isn't working label Aug 31, 2020
@placer14 placer14 changed the title Capture SyncIncomingBlocks as Chainwatch and Telegraf concern Restore SyncIncomingBlocks listening in Chainwatch Sep 1, 2020
@placer14 placer14 mentioned this issue Sep 1, 2020
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
kind/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Some more Chainwatch improvements filecoin-project/lotus
1 participant
@placer14