Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

chore: release: v1.15.2-rc2 #8533

Merged
merged 7 commits into from
May 2, 2022
Merged

chore: release: v1.15.2-rc2 #8533

merged 7 commits into from
May 2, 2022

Conversation

jennijuju
Copy link
Member

Related Issues

Proposed Changes

backport
#8531
#8511
#8526

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

  • All commits have a clear commit message.
  • The PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, test
    • area: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps
  • This PR has tests for new functionality or change in behaviour
  • If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in https://lotus.filecoin.io or Discussion Tutorials.
  • CI is green

masih and others added 4 commits April 22, 2022 02:46
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
@jennijuju jennijuju requested a review from a team as a code owner April 22, 2022 00:56
@jennijuju jennijuju force-pushed the jen/v1522 branch 14 times, most recently from 4f6fa7b to bd9e8c7 Compare April 23, 2022 20:19
@codecov
Copy link

codecov bot commented Apr 26, 2022

Codecov Report

Merging #8533 (48c5460) into release/v1.15.2 (dcf6f64) will increase coverage by 0.05%.
The diff coverage is 92.85%.

Impacted file tree graph

@@                 Coverage Diff                 @@
##           release/v1.15.2    #8533      +/-   ##
===================================================
+ Coverage            40.77%   40.82%   +0.05%     
===================================================
  Files                  686      686              
  Lines                75495    75500       +5     
===================================================
+ Hits                 30780    30820      +40     
+ Misses               39391    39361      -30     
+ Partials              5324     5319       -5     
Impacted Files Coverage Δ
build/version.go 27.27% <ø> (ø)
extern/sector-storage/tarutil/systar.go 42.10% <ø> (ø)
node/modules/storageminer_idxprov.go 82.35% <91.66%> (+6.26%) ⬆️
node/config/def.go 97.71% <100.00%> (ø)
chain/exchange/peer_tracker.go 66.66% <0.00%> (-4.31%) ⬇️
chain/sync_manager.go 73.91% <0.00%> (-0.63%) ⬇️
chain/store/store.go 65.00% <0.00%> (-0.50%) ⬇️
chain/messagepool/selection.go 83.07% <0.00%> (-0.39%) ⬇️
chain/sync.go 70.52% <0.00%> (-0.35%) ⬇️
node/impl/storminer.go 24.10% <0.00%> (-0.32%) ⬇️
... and 13 more

@jennijuju jennijuju merged commit ece51c5 into release/v1.15.2 May 2, 2022
@jennijuju jennijuju deleted the jen/v1522 branch May 2, 2022 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants