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: release: v1.28.0 #12271

Merged
merged 29 commits into from
Jul 24, 2024
Merged

build: release: v1.28.0 #12271

merged 29 commits into from
Jul 24, 2024

Conversation

rjan90
Copy link
Contributor

@rjan90 rjan90 commented Jul 22, 2024

Proposed Changes

  • Prep for cutting stable v1.28.0

Backports:

Checklist

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

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • Update CHANGELOG.md or signal that this change does not need it.
    • If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
    • If the change does not require a CHANGELOG.md entry, do one of the following:
      • Add [skip changelog] to the PR title
      • Add the label skip/changelog to the PR
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

rjan90 and others added 16 commits July 22, 2024 13:30
Update changelog
* Add support for nv23 in `lotus-shed migrate-state` cmd

Add support for nv23 in `lotus-shed migrate-state` cmd

* Add actors v14 to `check-invariants` cmd

Add actors v14 to `check-invariants` cmd
Use concrete/latest version of F3: v0.0.3
Upgrade to new version of OpenTelemetry to also play nice with F3.
Reduce the log level for `miner with id...` to DEBUG, since in normal
operation of F3 at least 5 messages are sent per epoch. In an event of
rebroadcast the number of messages broadcasted could surpass 10. Hence,
the `DEBUG` log level.
Upgrade to the latest go F3, with fix to default cert exchange config in
local devnet.
@rjan90 and @jennijuju reported seeing this log a lot, which prompted an investigation of the logic. This code does not implement [FIP-0023](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0023.md) correctly. Specifically, if we have the following mintickets:

```
ts1: 1, 2
ts2: 0,3
```

This code will incorrectly return ts1 as the "smaller" tipset, even though the tie should have been broken in favour of ts2 based on `1 > 0`.
Fix lint error: correct typo in F3Participation function comment
Corrected "successfull" to "successful" in comments and documentation to fix a lint error.
go mod tidy
Copy link
Member

@BigLep BigLep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is in draft and hasn't had a review request yet. I just left a couple of comments of things that saw in the CHANGELOG.

CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
rjan90 and others added 3 commits July 23, 2024 10:47
Co-authored-by: Steve Loeppky <biglep@protocol.ai>
Set Mainnet upgrade epoch NV23
Update changelog.md
@BigLep
Copy link
Member

BigLep commented Jul 23, 2024

@rjan90 : is #12248 making the cut?

@rjan90
Copy link
Contributor Author

rjan90 commented Jul 23, 2024

@rjan90 : is #12248 making the cut?

No, I suggest we drop that backport since it is not critical. Then the ascii-art can be an easter-egg for those running the master branch instead during the network upgrade :D

rjan90 added 2 commits July 23, 2024 21:56
…23 (#12276)

* Update to final GST for nv23

Update to final GST for nv23

* Bump filecoin-ffi to v1.28.0

Bump filecoin-ffi to v1.28.0

* Update CHANGELOG.md

Update CHANGELOG.md

* Update Builtin-actors to v14.0.0

Update Builtin-actors to v14.0.0
Update Changelog, version-string, make gen and make docsgen
@rjan90
Copy link
Contributor Author

rjan90 commented Jul 23, 2024

Waiting on this PR to be ready, as it needs to be backported - but opening for reviews in the meantime:

@rjan90 rjan90 marked this pull request as ready for review July 23, 2024 20:16
Re-run ./pack.sh v14 v14.0.0
@BigLep BigLep mentioned this pull request Jul 23, 2024
55 tasks
masih and others added 2 commits July 24, 2024 00:15
Register otel collector bridging to the default prometheus registry so
that F3 metrics (which use the newer otel APIs for metrics) get included
in Lotus metrics.
Update changelog with #12285 backport
@rjan90 rjan90 requested a review from aarshkshah1992 July 24, 2024 06:49
@aarshkshah1992
Copy link
Contributor

aarshkshah1992 commented Jul 24, 2024

@rjan90

@rvagg
Copy link
Member

rvagg commented Jul 24, 2024

A gentle +1 to removing those 2 additional backports - the first one was labelled mainly because it coupled with #12112 and it was originally marked for backporting but was subsequently unmarked. #12252 is not really critical either, even though it does nicely clean up the config file a bit more.

But fwiw I'm running both my mainnet and calibnet nodes on #12288 which is on top of this and it seems to be fine.

@rjan90
Copy link
Contributor Author

rjan90 commented Jul 24, 2024

A gentle +1 to removing those 2 additional backports

Yeah, I will remove those.

@ribasushi
Copy link
Collaborator

@rjan90 @rvagg @aarshkshah1992 If you end up reverting #12252 you will be knowingly reintroducing a configuration stack for a subsystem that does not exist. 2 minutes before the release.

This is not... smart.

@rjan90
Copy link
Contributor Author

rjan90 commented Jul 24, 2024

@rjan90 @rvagg @aarshkshah1992 If you end up reverting #12252 you will be knowingly reintroducing a configuration stack for a subsystem that does not exist. 2 minutes before the release.

This is not... smart.

Given our lengthy release cycles for network upgrades and the desire to minimize changes, even if it means temporarily retaining something like a stray config.

At this stage, with the majority advocating for removing the backport, I don't believe this is worth debating further. Our priority should be to get this release out, so that teams can begin integrating the NV23 changes into their stacks before the network upgrade, we can always address those cleanups in the next release.

* chore: f3: Upgrade to go-f3 `v0.0.5` (#12279)

* Upgrade to go-f3 `v0.0.5`

Upgrade to the latest version of go-f3 with initial power table storage with far enough lookback, and dynamic manifest persistence.

---------

Co-authored-by: Jakub Sztandera <oss@kubuxu.com>
Co-authored-by: Jiaying Wang <42981373+jennijuju@users.noreply.github.com>
Co-authored-by: Steven Allen <steven@stebalien.com>

* remove unwanted changelog

* fix import

* Revert "chore!: markets: remove deal constants"

This reverts commit d045ccb.

* Revert "chore: config: yet more lp2p removal from miner"

This reverts commit 70400c9.

* fix eth trace panic

* Update CHANGELOG.md

Co-authored-by: Jakub Sztandera <oss@kubuxu.com>

* Update CHANGELOG.md

---------

Co-authored-by: Masih H. Derkani <m@derkani.org>
Co-authored-by: Jakub Sztandera <oss@kubuxu.com>
Co-authored-by: Steven Allen <steven@stebalien.com>
Co-authored-by: Phi <orjan.roren@gmail.com>
Co-authored-by: aarshkshah1992 <aarshkshah1992@gmail.com>
@rjan90 rjan90 merged commit 28a578f into release/v1.28.0 Jul 24, 2024
78 checks passed
@rjan90 rjan90 deleted the phi/v1280-stable branch July 24, 2024 10:36
ribasushi added a commit to ribasushi/ci-abusing-lotus-fork that referenced this pull request Jul 24, 2024
ribasushi added a commit to ribasushi/ci-abusing-lotus-fork that referenced this pull request Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ☑️ Done (Archive)
Development

Successfully merging this pull request may close these issues.

9 participants