-
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
build: release: v1.28.2 #12392
build: release: v1.28.2 #12392
Conversation
Hopefully v1.28.2 will completely fix the pledge issue together. |
Is it already available? |
chore: bump versions and make gen/docsgen-cli
chore: update v1.282. changelog
* Update go-f3 to 0.2.0 Includes: - fix for excessive bandwidth usage - significant performance improvements - minor consensus fixes Signed-off-by: Jakub Sztandera <[email protected]> * add changelog Signed-off-by: Jakub Sztandera <[email protected]> * chore(f3): update to final released version --------- Signed-off-by: Jakub Sztandera <[email protected]> Co-authored-by: Steven Allen <[email protected]>
storage/pipeline.NewPreCommitBatcher and storage/pipeline.New now have an additional error return to deal with errors arising from fetching the sealing config.
error return to deal with errors arising from fetching the sealing config.
* Power is units of Space * Time so multiply by deal duration * fix: miner: Fix DDO pledge math * appease the changelog checker * Fix gen --------- Co-authored-by: zenground0 <[email protected]>
- Updated the logging statement in `testOutOfGasError` to correctly reference `build.BlockGasLimit` instead of `buildconstants.BlockGasLimit`.
fix: update changelog to reference bandwidth issue ticket
I think we should also make clear if we're going to backport additional fixes around pledging like what was proposed in #12386 |
Co-authored-by: Steve Loeppky <[email protected]>
IIUC we won't? |
I think I missed some of the details about backporting and what has been done is good. #12395, which was backported, was informed by #12386 I don't see any issues at a high level. Thanks for handling. |
#12379
This patch includes: