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
..
common_actors.go	fix(chainwatch): Actually capture human actor names	2020-08-18 00:22:01 -04:00
market.go	fix(chainwatch): fix deadlock in sector deals	2020-08-27 11:47:53 -07:00
messages.go	fix(chainwatch): Error instead of panic during processing	2020-09-03 19:15:19 -04:00
miner.go	perf(chainwatch): parallelize miner processing	2020-08-28 13:26:11 -07:00
mpool.go	polish(chainwatch): clean up logging	2020-08-27 11:47:53 -07:00
power.go	feat(chainwatch): Add more complete power and reward metrics	2020-08-27 23:00:12 -04:00
processor.go	fix(chainwatch): Stop SyncIncomingBlocks from leaking into processing	2020-09-03 19:15:25 -04:00
reward.go	feat(chainwatch): Add more complete power and reward metrics	2020-08-27 23:00:12 -04:00