-
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
[Test do not merge] Docker build in releases branch #11561
Closed
Closed
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
…e future confusion (#11371)
add main net upgrade epoch
chore: watermelon: upgrade epoch
Record currentSize on addLocked
Update unreleased changelog
…11309) - Added a goroutine to listen for interrupt signals, which will cancel the current context when an interrupt signal is received. This allows for graceful shutdown of ongoing operations.
feat: metric: export Mpool message count
…11382) * chore: eth: move & rename input/output encoding functions These are shared functions, so I'm moving them to the utils library. * fix: eth: correctly encode and simplify native input/output encoding When generating eth traces, we encode "native" message inputs/outputs to "solidity ABI" by formatting the inputs/outputs the same way we do in FEVM's "handle_native_method". However, we had quite a few bugs with the implementation: 1. We were right-aligning 64bit values in 256bit words, instead of left-aligning (as we should given that these values are big-endian). 2. The return-value encoding wasn't correctly handling lengths. This patch: 1. Fixes those bugs. 2. Deduplicates the logic (we're doing _basically_ the same thing in both cases). 3. Removes all error paths (these functions can't fail).
feat: sealing: load SectorsSummary from sealing SectorStats instead of calling API each time
Add backports to changelog
release: v1.25.1-rc1
Also explicitly limit how many bytes we're willing to read in one go such that we're capable of reading a worst-case tipset (like, really, never going to happen worst-case). Previously, this wasn't an issue. However, we've bumped the max number of messages from 8,192 to 150,000 and need to limit allocations somewhere else.
It's not a const for the testground build, and needs to be an int 99% of the time. So we might as well just cast here.
build: v1.25.2-rc1
fix: lotus-provider: show addresses in log
fix: lotus-provider: Wait for the correct taskID
harmony: Fix task reclaim on restart
fix: lotus-provider: Fix log output format in wdPostTaskCmd
do not suggest the default layer
This reverts commit 3569e4e.
…-update-libp2p chore:libp2p:update libp2p deps in release-v1.25.2
backports: lotus-provider: fixes caught in rc1-testing
feat: syncer: optimize syncFork for one-epoch forks
…post-err fix: wdpost: fix vanilla proof indexes
chore: backports to `release/v1.25.2`
fix: docs: Modify generate-lotus-cli.py to ignoring aliases.
Bump version and changelog
release: v1.25.2
backport: docker build fix for v1.25.2
Closing the test, as the builds now work |
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.
Additional Info
Testing docker-build after #11559 was merged/backported
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