Ran automatically via:
go get github.com/cosmos/cosmos-sdk/crypto/ledger@v0.45.11
Fixes:
=> ERROR [15/16] RUN make client 0.7s
------
> [15/16] RUN make client:
0.202 building wormchaind-v0.0.1
0.202 go build -v -ldflags '-X github.com/cosmos/cosmos-sdk/version.Name=wormchain -X github.com/cosmos/cosmos-sdk/version.ServerName=wormchaind -X github.com/cosmos/cosmos-sdk/version.Version=v0.0.1 -X github.com/cosmos/cosmos-sdk/version.Commit=abc123 -X "github.com/cosmos/cosmos-sdk/version.BuildTags=ledger"' -tags ledger -o build/wormchaind cmd/wormchaind/main.go
0.649 /go/pkg/mod/github.com/wormhole-foundation/cosmos-sdk@v0.45.9-wormhole-2/crypto/ledger/ledger_real.go:6:8: missing go.sum entry for module providing package github.com/cosmos/ledger-cosmos-go (imported by github.com/cosmos/cosmos-sdk/crypto/ledger); to add:
0.649 go get github.com/cosmos/cosmos-sdk/crypto/ledger@v0.45.11
0.650 make: *** [Makefile:26: build/wormchaind] Error 1
------
Dockerfile:37
--------------------
35 | RUN /bin/bash /app/devnet/create-genesis.sh
36 |
37 | >>> RUN make client
38 | RUN chmod +x /app/build/wormchaind
39 |
--------------------
ERROR: failed to solve: process "/bin/sh -c make client" did not complete successfully: exit code: 2
* node: update quic-go
Ran via:
go get github.com/quic-go/quic-go@v0.42.0
* node: update mongo-drive dependency
Ran via:
go get go.mongodb.org/mongo-driver@latest
* node: upgrade libp2p-go
Ran via:
go get github.com/libp2p/go-libp2p@v0.33.1
Refs: #3863
* node: fallout from the go upgrade in the go.sum
Run via:
go mod tidy
This updates the go.sum and removes unnecessary indirect references.
* docs: use go1.21.8
* github: use go1.21.8
Except for wormchain.
* node: update dockerfiles to use go 1.21.8
This was done with scripts/update-go-version.sh
* scripts: update linter dockerfile to use go 1.21.8
This was done with scripts/update-go-version.sh
* wormchain: update ibc-relayer to use go 1.21.8
This was done with scripts/update-go-version.sh
* scripts: add update-go-version.sh
This is a little helper to make updating the version of go a bit nicer.
* scripts: update-go-version.sh fixes
* set the default docker command to "dokcer"
* update the comment for the humongous sed command for dockerfiles
* github: fix go linting
* Upgrade golangci-lint to a version built with go 1.21.x. The older
version was a binary version built with go 1.20.x and it was failing
against the newer code built with go 1.21.x
* print the golangci-lint version in each run to see what version of go
it was built with in case there are incompatibilties during the next
upgrade
* remove the linter config skipping over pkg/supervisor entirely and
instead put in an override to ignore the `unused` linter for the
pkg/supervisor testhelpers bits for unsed test functions necessary
to satisfy the test interface.
* scripts: update golang linter cli invocation
* github: use the latest version of golangci-lint
Because 1.52.2 is built with go 1.20.x which has issues with this project
now that it is upgraded to 1.21.8.
* node: remove implicit memory aliasing in a loop
Caught by an upgraded golangci-lint with the gosec linter:
::medium file=node/pkg/watchers/evm/connectors/batch_poller.go,line=226,col=8::G601: Implicit memory aliasing in for loop. (gosec)
::medium file=node/pkg/watchers/evm/connectors/batch_poller.go,line=285,col=8::G601: Implicit memory aliasing in for loop. (gosec)
::medium file=node/pkg/watchers/evm/connectors/batch_poller_test.go,line=128,col=37::G601: Implicit memory aliasing in for loop. (gosec)
See also: https://husni.dev/beware-of-implicit-memory-aliasing-in-go-foor-loop/
* node: update logging
* Update go to 1.21.9
Automated via:
scripts/update-go-version.sh 1.21.9
* node: update test root context teardown time
Otherwise things get really sad.
* scripts: additions to update-go-versions.sh
* Standardized on prefacing functions with `function` for consistency
* Added a few more comments to explain how things work
* Automatically increment the go version and toolchain in go.mod
* Standardized on prefacing functions with `function` for consistency
* Make the go image debian version a variable for ease of maintenance
* node: update go.mod to specify 1.21.9
* node: update node tests
Review feedback from @pires
* scripts: run go mod tidy in update-go-version.sh
Required after running go mod edit or it refuses to build.
* node: update go.mod
Running `go mod tidy` removes the toolchain so the build works.
* node: update node tests
---------
Co-authored-by: Ryan Hamphrey <hamphreyryan26@gmail.com>
* deployments: update for guardian set index v4
Wormholescan returns vaas base64 encoded, but guardianSetVAAs.csv
has them in hex format. This is the correct command to download a
guardian set upgrade vaa and convert it to hex in one go:
curl -sq 0000000000000000000000000000000004/18252082506122526004 | \
jq .vaaBytes -r | \
base64 -d | \
xxd -p | \
tr -d '\n'
echo
Refs: wormhole-foundation/wormhole-networks#53
* node: update admin template gsti to 4
Refs: wormhole-foundation/wormhole-networks#53
* eth: deploy with forge
* Delete unused scripts
* Support upgrade, bytecode verify and publish tool
* Add script to register all chains on a new chain
When behind a private network such as in the case of a guardian running
in Kubernetes, or behind a NAT, the default p2p setup doesn't work. It
looks at all addresses that it is listening on and advertises them on p2p
as the addresses for contacting the guardian. This patch is the first
step towards allowing specifying a custom ip address to be advertised on
the gossip p2p network.
For example, a guardian running inside kubernetes can post a reserved ip
address of the incoming ingress/load balancer that sends the traffic in
to their guardian.
* CI: Change chain id for evm devnet node
* Set env file to match devnet configured ethereum chain id
* set evm chain id to ganache default
* update test evm chain ids in evm tests
* Add cspell configuration and custom dictionary
The goal is to cut down on both incoming tyops, and well meaning but
spammy tyop fix PRs.
To run cspell locally install it and run:
cspell '**/*.md' \
--config cspell.config.yaml \
--words-only \
--unique \
--quiet | sort --ignore-case
* docs: cspell updates
* wormchain: cspell updates
* aptos: cspell updates
* node: cspell updates
* algorand: cspell updates
* whitepapers: cspell updates
* near: cspell updates
* solana: cspell updates
* terra: cspell updates
* cosmwasm: cspell updates
* ethereum: cspell updates
* clients: cspell updates
* cspell updates for DEVELOP document
* github: run cspell github action
* sdk: cspell updates
* github: only run cspell on markdown files
* algorand: EMMITTER --> EMITTER
Suggested-by: @evan-gray
* cspell: removed from dictionary
Suggested-by: @evan-gray
* aptos and node: cspell updates
Suggested-by: @evan-gray
* cosmowasm: doc updates for terra2
Suggested-by: @evan-gray
* algorand: cspell updates
Suggested-by: @evan-gray
* algorand: cspell updates
Suggested-by: @evan-gray
* cspell: updated custom word dictionary
This resorts the dictionary and adds a few new words from the
algorand/MEMORY.md document around varints and integers.
* cspell: sort the dictionary how vscode does it
On macOS the sorting is locale dependent. To do this on macOS, you have
to invert the case, do a character insensitive sort, and then invert the
case again:
LC_COLLATE="en_US.UTF-8" cspell '**/*.md' --config cspell.config.yaml \
--words-only \
--unique \
--no-progress \
--quiet \
| tr 'a-zA-Z' 'A-Za-z' \
| sort --ignore-case \
| tr 'a-zA-Z' 'A-Za-z'
This requires the `LC_COLLATE` variable to be set to `en_US.UTF-8`, or it
will not do the right thing.
* docs: grammar clean up
---------
Co-authored-by: Evan Gray <battledingo@gmail.com>
Csongor Kiss
Bruce Riley
Jeff Schroeder
Michael Nguyen
bruce-riley
Csongor Kiss
Nikhil Suri
Dirk Brink
djb15
Evan Gray
Martin Vejmelka
Ben Guidarelli
A5 Pickle
scnale