lotus/chain/exchange
Steven Allen 4d73febaf7
chore: sync: cleanup sync serve and reduce log noise (#11543)
* chore: cleanup sync serve and reduce log noise

1. Demote a noisy blocksync request error to debug. All this warning
means is that someone is requesting a tipset we don't have.
2. Add a separate warning if we fail to collect a chain. If we have the
tipsets but fail to collect the chain, something is actually wrong.
3. Fix a TODO and return a single CompactedMessages rather than 4
separate values.

* generally reduce the warning to info

It turns out we do fail to gather messages frequently as well, likely
because we have written the tipsets but haven't fetched the messages...
2024-01-29 11:17:05 -08:00
..
cbor_gen.go fix: exchange: allow up to 10k messages per block 2023-12-09 18:08:32 +09:00
client.go feat: exchange: change GetBlocks to always fetch the requested number of tipsets 2024-01-10 12:04:52 -05:00
doc.go fix make gen 2022-08-29 16:25:30 +02:00
interfaces.go feat: exchange: change GetBlocks to always fetch the requested number of tipsets 2024-01-10 12:04:52 -05:00
peer_tracker.go Don't use go-libp2p-core 2022-08-25 14:20:41 -04:00
protocol_encoding.go fix: exchange: explicitly cast the block message limit const (#11511) 2023-12-09 23:24:43 +09:00
protocol.go fix: exchange: allow up to 10k messages per block 2023-12-09 18:08:32 +09:00
server.go chore: sync: cleanup sync serve and reduce log noise (#11543) 2024-01-29 11:17:05 -08:00