lotus/cmd/lotus-chainwatch
Mike Greenberg abaef98fd8 fix(chainwatch): Stop SyncIncomingBlocks from leaking into processing
The SQL query was anchoring data from the `blocks` table, which includes
all blocks seen from SyncIncomingBlocks which isn't always available in
the chainstate via the API. In order to prevent these blocks from
leaking into normal processing (which errors anyway), the join was
changed to allow `blocks_synced` to anchor the set as we originally
intended.
2020-09-03 19:15:25 -04:00
..
processor fix(chainwatch): Stop SyncIncomingBlocks from leaking into processing 2020-09-03 19:15:25 -04:00
scheduler feat(chainwatch): Add more complete power and reward metrics 2020-08-27 23:00:12 -04:00
syncer fix(chainwatch): Add important documentation 2020-08-31 22:55:11 -04:00
util polish(chainwatch): accept lotus api and token 2020-08-27 14:05:39 -07:00
dot.go fix(log): Move metrics and stage updates to debug; Add --log-level switch 2020-07-16 11:36:52 -04:00
main.go polish(chainwatch): accept lotus api and token 2020-08-27 14:05:39 -07:00
run.go Merge pull request #3275 from filecoin-project/fix/chainwatch/sync 2020-08-28 12:16:00 +02:00