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: merge releases back into master #10999

Merged
merged 41 commits into from
Jun 21, 2023

Conversation

shrenujbansal
Copy link
Contributor

Related Issues

Proposed Changes

Additional Info

Checklist

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

  • Commits have a clear commit message.
  • 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, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

Shrenuj Bansal and others added 30 commits May 3, 2023 17:20
Hide lotus-miner legacy markets cmds
Make docsgen-cli
* Fix 1.21 regression: GET_32G_MAX_CONCURRENT + mixed prepared/executing leads to stuck scheduler

If you have 12 GET tasks and GET_32G_MAX_CONCURRENT=1, sealing jobs will only show assigned tasks for GET of the miner
and is stuck.
I believe this to be a regression of 1.21 unifying the counters, in the case of GETs where PrepType and TaskType
both being seal/v0/fetch leading to a state where tasks are blocked since already counted towards the limit.

* itests: Repro issue from PR #10633

* make counters int (non-working)

* fix: worker sched: Send taskDone notifs after tasks are done

* itests: Make TestPledgeMaxConcurrentGet actually reproduce the issue

* make the linter happy

---------

Co-authored-by: Steffen Butzer <steffen.butzer@outlook.com>
Changelog and build version for 1.23.1-rc2
Check if epoch is negative in GetTipsetByHeight
This PR introduces as sharded mutex within the ChainIndex#GetTipsetByHeight.
It also replaces a go map with xsync.Map which doesn't require locking.

The lock is taken when it appears that ChainIndex filling work should be
started. After claiming the lock, the status of the cache is rechecked,
if the entry is still missing, the fillCache is started.

Thanks to @snissn and @arajasek for debugging and taking initial stabs at this.

Supersedes #10866 and 10885

Signed-off-by: Jakub Sztandera <kubuxu@protocol.ai>
Signed-off-by: Jakub Sztandera <kubuxu@protocol.ai>
…3.1-rc3

feat: chainstore: sharded mutex for filling chain height index
…kport

chore: deps: update to go-libp2p 0.27.5
chore: update build version and changelog for 1.23.1-rc4
shrenujbansal and others added 11 commits June 5, 2023 19:07
chore: update changelog title and comments
…ent-rel

Add comment stating msgIndex is an experimental feature
Update changelog before publishing
Remove old upgrade warnings. Instead call-out that users should read the upgrade warnings section in the v1.23.0 release if upgrading from v1.22.1
Add link to LOTUS_FVM_CONCURRENCY docs
chore: Update build version and changelog for final 1.23.1 cut
@shrenujbansal shrenujbansal requested a review from a team as a code owner June 21, 2023 13:36
@shrenujbansal shrenujbansal merged commit 8b849e6 into master Jun 21, 2023
@shrenujbansal shrenujbansal deleted the sbansal/merge-releases-to-master-20230621 branch June 21, 2023 20:43
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.

7 participants