v1.28.0-dev

What's Changed

• feat: Add skeleton for nv23 by @rjan90 in #454

Full Changelog: ed08caa...v1.28.0-dev

081367cae7cdfe87

feat: Add skeleton for nv23 (#454)

* Add nv23-skeleton

Add nv23-skeleton

* Update cargo.lock

Ran: `cargo update -p "filecoin-proofs-api@17.0.0"`

v1.27.0-rc2

What's Changed

• chore: deps: update to go-state-types 0.13.1 by @arajasek in #451
• feat: update to the improved error handling in proofs by @cryptonemo in #450

Full Changelog: 5868337...v1.27.0-rc2

ed08caaf8778e1b6

Merge pull request #450 from filecoin-project/improved-error-handling

feat: update to the improved error handling in proofs

v1.27.0-rc1

What's Changed

• Make sure we can reach the user's requested FVM concurrency by @Stebalien in #449

Full Changelog: v1.26.0...v1.27.0-rc1

5868337f70cdf3c9

Make sure we can reach the user's requested FVM concurrency (#449)

We previously used the FVM's `ThreadedExecutor` to execute messages on
separate threads because the FVM requires 64MiB of stack space.

1. The FVM v3 supported for 8 concurrent threads.
2. The FVM v4 supports up to the number of CPU threads available.

Unfortunately, neither version was influenced by the
`LOTUS_FVM_CONCURRENCY` environment variable.

This patch fixes this by:

1. Moving the thread-pool to the FFI itself (sharing it between FVM
versions).
2. Setting the thread-pool size equal to `LOTUS_FVM_CONCURRENCY`.

It also defaults `LOTUS_FVM_CONCURRENCY` to the number of available
CPU threads instead of the previous 4.

NOTE: I've also tried increasing the stack size instead of using
threads, but Go _does not_ like it when other foreign mess with the
stack size of _its_ threads (but it has no problem if we create our own
threads).

fixes https://github.com/filecoin-project/lotus/issues/11817

v1.26.0

This is a re-tag of v1.26.0-rc2 for the final release of lotus v1.26.

v1.26.0-rc2

What's Changed

• Update FVMv4 to v4.1.2 to support FIP-0083.
• Update FVMv3 to restore some tracing information back to the launch of FEVM.

Full Changelog: v1.26.0-rc1...v1.26.0-rc2

b715c9403faf919e

chore: update FVM to v4.1.2 and v3.9.0 (#447)

* chore: update FVM to v4.1.2

chore: update FVM to v4.1.2

* chore: update fvm v3

This brings back the InvokeActor event to the v3 trace, but with all the new information we get in v4.

Co-authored-by: Steven Allen <steven@stebalien.com>

v1.26.0-rc1

What's Changed

• fix: list GPU devices also with SupraSeal by @vmx in #444
• refactor: clean up deps by @vmx in #445
• build(deps): bump golang.org/x/crypto from 0.1.0 to 0.17.0 by @dependabot in #443
• chore: use auth_header when trying to download release tarball by @galargh in #310
• Update the FVM to v4.1 by @Stebalien in #446

New Contributors

• @galargh made their first contribution in #310

Full Changelog: 4176a1e...v1.26.0-rc1