lotus/node
Masih H. Derkani d044e30e12 Infer index provider topic from network name by default
Index provider integration uses a gossipsub topic to announce changes to
the advertised content. The topic name was fixed to the default topic
which is `/indexer/ingest/mainnet`.

In the case of lotus, the gossipsub validators enforce a list of topics
the instance is permitted to join by setting subscription filter option
when `PubSub` instance is constructed via DI.

Having the fixed topic name meant that any SP starting up a node on a
network other than `mainnet` would have to override the default config
to avoid the node crashing when index provider is enabled.

Instead of a fixed default, the changes here infer the allowed indexer
topic name from network name automatically if the topic configuration is
left empty.

Fixes #8510
2022-04-22 02:46:05 +02:00
..
config Infer index provider topic from network name by default 2022-04-22 02:46:05 +02:00
hello Plumb contexts through 2021-12-11 17:04:00 -05:00
impl feat: cli: lotus client list-asks --protocols 2022-04-11 19:49:52 +02:00
modules Infer index provider topic from network name by default 2022-04-22 02:46:05 +02:00
repo Merge remote-tracking branch 'origin/master' into feat/post-worker 2022-03-21 12:09:47 +01:00
builder_chain.go Rename the Lotus VM to LegacyVM 2022-03-15 19:40:17 -04:00
builder_miner.go Fix DI of PubSub in markets by binding dependencies it needs 2022-04-07 11:06:29 -04:00
builder.go resolve merge conflicts with master 2022-03-18 12:28:22 +01:00
fxlog.go
options.go chain: Cleanup consensus logic 2021-09-02 18:09:37 +02:00
rpc.go retrieval: REST export endpoint 2021-11-22 12:46:17 +01:00
shutdown_test.go feat: Add additional test annotations (#8272) 2022-03-16 18:37:34 +01:00
shutdown.go decouple rpc server and shutdown logic from cmd. 2021-05-21 21:34:17 +01:00
testopts.go enable libp2p options 2021-06-30 12:55:43 +02:00