-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: merge releases back to master #8468
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat: config: enable indexer providing by default
…nap-worker-cleanup backport: v1.15.1: feat: sealing: Sector upgrade queue
…snap-queue backport: v1.15.1: feat: sealing: Sector upgrade queue
FVM integration
Always set index provider options based on the lotus configuration. Otherwise, they will have no effect.
The markets process instantiates its own `PubSub` instance with all validators, peer scoring, etc. set up. Use that instane to join the indexing topic, otherwise the default topic instantiated by index-provider internally (via go-legs) has no validators.
Bind drand and bootstrap peers config so that `PubSub` instantiated by `ConfigCommon` has all the dependencies it needs when `PubSub` instance is needed in markets. In ths case, the instance is needed by the index provider engine to announce new indexing advertisements.
fix: FVM: add finality check for consensus faults
build: release: v1.15.1-rc6
chore: release: v1.15.1 prep
build: release: v1.15.1
jennijuju
force-pushed
the
jen/mergeback
branch
from
April 11, 2022 23:24
b13f519
to
0dcad9c
Compare
jennijuju
force-pushed
the
jen/mergeback
branch
2 times, most recently
from
April 12, 2022 11:52
f508d1e
to
137f494
Compare
magik6k
reviewed
Apr 12, 2022
jennijuju
force-pushed
the
jen/mergeback
branch
2 times, most recently
from
April 12, 2022 13:29
dca6566
to
1fc94e3
Compare
fix merge error Co-authored-by: Łukasz Magiera <magik6k@users.noreply.github.com>
magik6k
approved these changes
Apr 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
Proposed Changes
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
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, testarea
: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps