-
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
release: v1.23.3 #11109
release: v1.23.3 #11109
Conversation
…lotus into ianconsolata-id/remove-dockerfile.lotus
deps: Update go-jsonrpc to v0.3.1
…ubscribe-and-filter-methods Make (un)subscribe and filter RPC methods require only read perm
Make lotus-fountain UI slightly friendlier
…t-syncds fix: tests: Use mutex-wrapped datastore in storage tests
feat: deflake eth_balance_test
fix: remove invalid field UpgradePriceListOopsHeight
* Validate that FromBlock/ToBlock epoch is indeed a hex value * Adding tests
…acts fix: ci: Debugging m1 build
libp2p: add QUIC and WebTransport to default listen addresses
chore: update go-libp2p to v0.27.3
feat: fix deadlock in splitstore-mpool interaction
* 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 <[email protected]>
This reverts commit 0a064c1.
Co-authored-by: Friðrik Ásmundsson <[email protected]>
feat: changelog: add details of tracer experiment
chore: backport improvements to the consensus slasher
CHANGELOG.md
Outdated
- [Lotus now includes a Slasher tool](https://github.com/filecoin-project/lotus/pull/10928) to monitor the network for Consensus Faults, and report them as appropriate | ||
- The Slasher investigates all incoming blocks, and assesses whether they trigger any of the three Consensus Faults defined in the Filecoin protocol | ||
- If any faults are detected, the Slasher sends a `ReportConsensusFault` message to the faulty miner | ||
- For more information on the Slasher, including how to run it, please see LINK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: link after updating docs with changes in #11126
CHANGELOG.md
Outdated
- Added new environment variable `LOTUS_EXEC_TRACE_CACHE_SIZE` to configure execution trace cache size ([filecoin-project/lotus#10585](https://github.com/filecoin-project/lotus/pull/10585)) | ||
- If unset, we default to caching 16 most recent execution traces. Storage Providers may want to set this to 0, while exchanges may want to crank it up. | ||
- The tracer's Elastic Search transport has been upgraded to support batch traces: [filecoin-project/lotus#10405](https://github.com/filecoin-project/lotus/pull/10405) | ||
- This facilitates an experiment being run by ProbeLab [to measure the performance of the Gossipsub protocol in the Filecoin network](https://www.notion.so/pl-strflt/Write-explainer-doc-for-SPs-183a7775406d451a8b19e3cdc2cdf5c3?d=d8df4e142b78427ab470db68877da1ba#abba19208e3b4420a6388df7a3a48b62). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace link with #11118
CHANGELOG.md
Outdated
- If unset, we default to caching 16 most recent execution traces. Storage Providers may want to set this to 0, while exchanges may want to crank it up. | ||
- The tracer's Elastic Search transport has been upgraded to support batch traces: [filecoin-project/lotus#10405](https://github.com/filecoin-project/lotus/pull/10405) | ||
- This facilitates an experiment being run by ProbeLab [to measure the performance of the Gossipsub protocol in the Filecoin network](https://www.notion.so/pl-strflt/Write-explainer-doc-for-SPs-183a7775406d451a8b19e3cdc2cdf5c3?d=d8df4e142b78427ab470db68877da1ba#abba19208e3b4420a6388df7a3a48b62). | ||
- Users are invited to opt into the experiment by following the instructions [here](https://www.notion.so/pl-strflt/Write-explainer-doc-for-SPs-183a7775406d451a8b19e3cdc2cdf5c3?pvs=4#092a3a68d6734a12961f5c3fe95767e5) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above - can we give a tldr on why we encourage user to run this please?
chore: deps: update go-libp2p to v0.27.8
chore: deps: update to go-libp2p 0.27.9
fix: v1.23.3: go version increase
74b43ee
to
aa55e41
Compare
aa55e41
to
9c27d67
Compare
Related Issues
Closes #11048
Proposed Changes
Merge the release branch into releases, from where we'll be cutting the final release.
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, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps