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

build: backport changes to release/v1.30.0 branch #12663

Merged
merged 10 commits into from
Nov 6, 2024

Conversation

rjan90
Copy link
Contributor

@rjan90 rjan90 commented Oct 31, 2024

Related Issues

#12480

Proposed Changes

Backports PRs that has landed with a backport label on them to the release/v1.30.0 branch: https://github.com/filecoin-project/lotus/pulls?q=is%3Apr+label%3Arelease%2Fbackport+is%3Aclosed.

In preparation for cutting the stable v1.30.0 release.

PRs in question:

Checklist

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

rjan90 and others added 5 commits October 31, 2024 13:15
…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
- Sets UpgradeTuktukHeight to epoch 4461240
- Sets F3BootstrapEpoch to epoch 4501560
…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
@rjan90
Copy link
Contributor Author

rjan90 commented Nov 4, 2024

Missing this backport:

@rjan90 rjan90 marked this pull request as ready for review November 4, 2024 07:36
Implement `lotus f3` CLI sub commands:

* `manifest` to dump the current F3 manifest in either JSON or text.
* `list-miners` to list the current F3 participants.
* `status` to print summary status of F3.

Part of #12607

(cherry picked from commit 38e4d91)
* 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)
@masih
Copy link
Member

masih commented Nov 4, 2024

  • This gave me a lot of conflicts and due to the late addition of back port-label.

Cherrypicked.

I also backported:

@rjan90 rjan90 added the skip/changelog This change does not require CHANGELOG.md update label Nov 5, 2024
Kubuxu and others added 3 commits November 6, 2024 16:05
using `LOTUS_DISABLE_F3_PASSIVE_TESTING=1`

Signed-off-by: Jakub Sztandera <[email protected]>
chore: change F3BootstrapEpoch to -1
Upgrade to the latest go-f3 in prep for lotus release.
@rjan90 rjan90 enabled auto-merge (rebase) November 6, 2024 11:21
@rjan90 rjan90 disabled auto-merge November 6, 2024 12:23
@rjan90 rjan90 merged commit a9fa79b into release/v1.30.0 Nov 6, 2024
86 checks passed
@rjan90 rjan90 deleted the phi/backport-stable-v1300 branch November 6, 2024 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip/changelog This change does not require CHANGELOG.md update
Projects
Status: ☑️ Done (Archive)
Development

Successfully merging this pull request may close these issues.

4 participants