* add a basic FEVM integration test.
Exercises f4 addresses, placeholder transitions, Ethereum Account.
* remove unused parameter from newEthTxFromFilecoinMessageLookup.
* break when found in newEthTxFromFilecoinMessageLookup.
* fixup test.
* lint and gen.
* move test to itests root package.
Co-authored-by: Shrenuj Bansal <shrenuj.bansal@protocol.ai>
* Add f4 integration test and cli to generate eth addr from code
* make gen and docsgen
* fix lint
* address comments
* make gen and make docsgen sigh
* address moar comments
* use existing APIs to determine actor types
* Add IsEvmActor API
* "strings are bad" -Geoff
This discontinues packer builds and stops publishing (or attempting to
publish) them to AWS / DO. These have been broken for more than 6
months, and no one seems to have complained or even noticed, which seems
to indicate they are not being used much. For cloud platfrom support, we
can optionally write docker / terraform automation that folks could use
to more easily launch instances to cloud environments instead.
We have this env varible set in the project settings as well as the
CircleCI context. Due to what seems like a bug on CircleCI's eng, the
using the context causes our release flow to halt when some member of
the team initiate releases, but not others. So for now, it's safest to
rely on the project settings, which definitely won't cause this issue.
This completely removes publishing to Amamzon ECR. ECR is a private
docker repository (like DockerHub), but since it's private is can only
be used internally by PL teams to launch lotus nodes on AWS
infrastructure. No one currently seems to be using it. All the usual
suspects (Boost, Lotus, Infra) have been asked specifically, and said
they don't, and post has been made in the #engres channel to try and
catch anyone else. No one responded saying we should save it.
Goreleaser checks to make sure we don't have a dirty git state when
releasing, which means the kubo download we use to set up IPFS should be
removed before release.
* unknown return types should not be treated as errors from WaitForMessage
* simplecoin FEVM smoke test
* add itest-fevm to circle matrix
* use a named error for metadata lookup failures
* hand-write the fevm basic test
* make gen
* address nits
This is a major refactor of our dockerfile to support the following
- The lotus image will remain as is.
- The lotus-test image will be deprecated.
- The lotus-all-in-one image will also ship with the lotus-seed and lotus-fountain binaries, which it currently does not.
- The lotus-all-in-one image will be built in debug, calibnet, and butterflynet modes in addition to the (current) mainnet mode.
- The lotus-all-in-one image will now be published regularly using the following tags:
- 1.18.0-rc1 , 1.18.0-rc1-debug, 1.18.0-rc1-calibnet, 1.18.0-rc1-butterflynet . This pattern will be used for all lotus releases, including RC releases.
- nightly, nightly-debug, nightly-calibnet, nightly-butterflynet
- stable, stable-debug, stable-calibnet, stable-butterflynet
