-
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: backport changes to release/v1.30.0
branch
#12663
Commits on Oct 31, 2024
-
chore: update GST, Filecoin-FFI and Actors to final versions NV24 (#1…
…2658) * chore: bump GST to v0.15.0 chore: bump GST to v0.15.0 * chore: bump filecoin-ffi to v1.30.0 chore: bump filecoin-ffi to v1.30.0 * chore: update builtin-actors to v15.0.0 chore: update builtin-actors to v15.0.0
Configuration menu - View commit details
-
Copy full SHA for 5a6edf1 - Browse repository at this point
Copy the full SHA 5a6edf1View commit details -
chore: set nv24 upgrade epochs (#12660)
- Sets UpgradeTuktukHeight to epoch 4461240 - Sets F3BootstrapEpoch to epoch 4501560
Configuration menu - View commit details
-
Copy full SHA for ee916fd - Browse repository at this point
Copy the full SHA ee916fdView commit details
Commits on Nov 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 8364329 - Browse repository at this point
Copy the full SHA 8364329View commit details -
fix(api): make stick sessions actually work and make them non-racy (#…
…12665) * fix(api): make stick sessions actually work and make them non-racy We apparently have a way to specify that all "related" requests should go to the same node. However: 1. It didn't work at all. All future requests would go to the first successful node from the first request. Because that's how stack variables work. 2. It was racy if the context was re-used concurrently. But only the first time, see point 1. * test(api): test the API merge proxy 1. Test whether or not it works. 2. Test stickiness. * fix(api): update OnSingleNode documentation
Configuration menu - View commit details
-
Copy full SHA for 8fd2d51 - Browse repository at this point
Copy the full SHA 8fd2d51View commit details -
fix(f3): when returning a partially used lease, trim its ValidityTerm (…
…#12667) Signed-off-by: Jakub Sztandera <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 19a9d2d - Browse repository at this point
Copy the full SHA 19a9d2dView commit details -
Implement Lotus F3 CLI commands for general diagnostics (#12617)
Configuration menu - View commit details
-
Copy full SHA for bf725c7 - Browse repository at this point
Copy the full SHA bf725c7View commit details -
Conditionally change the limit of F3 certs listed via CLI (#12669)
* When no range is given, default limit to 10 * Otherwise default to unlimited. This is better than the current default of always unlimited because: * there are a lot of certs, and * when range is given the chances are the user wants all of them. Addresses #12627 (comment) (cherry picked from commit 773efae)
Configuration menu - View commit details
-
Copy full SHA for 8646c2f - Browse repository at this point
Copy the full SHA 8646c2fView commit details
Commits on Nov 6, 2024
-
feat(f3): allow to disable f3 passive testing (#12672)
using `LOTUS_DISABLE_F3_PASSIVE_TESTING=1` Signed-off-by: Jakub Sztandera <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 2cc2578 - Browse repository at this point
Copy the full SHA 2cc2578View commit details -
chore: change F3BootstrapEpoch to -1 (#12673)
chore: change F3BootstrapEpoch to -1
Configuration menu - View commit details
-
Copy full SHA for d477919 - Browse repository at this point
Copy the full SHA d477919View commit details -
Upgrade to go-f3
v0.7.2
(#12676)Upgrade to the latest go-f3 in prep for lotus release.
Configuration menu - View commit details
-
Copy full SHA for e27da57 - Browse repository at this point
Copy the full SHA e27da57View commit details