hyperlane-monorepo

Commit Graph

Author	SHA1	Message	Date
Trevor Porter	f76984baa5	fix: update warp monitors with latest registry to fix collateral value (#4849 ) ### Description - To include some fixes to the coinGeckoIds of warp routes recently merged into the registry ### Drive-by changes - made an agent metrics log `warn`, which helped debugging some recent issues - Update the eclipsemainnet owner in owners.ts, a mostly symbolic change as this isn't actually used in our tooling in infra ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	2 weeks ago
J M Rossy	e89030de30	chore: Upgrade yarn to 4.5.1 (#4818 ) Upgrade yarn 4.0.2 -> 4.5.1 for latest security fixes	3 weeks ago
Paul Balaji	a028e16243	chore: migrate away from unmaintained rust toolchain installer (#4465 ) chore: migrate away from unmaintained rust toolchain installer - previous toolchain action was archived almost a year ago https://github.com/actions-rs/toolchain - new action has 1k+ stars and sensible defaults https://github.com/dtolnay/rust-toolchain - uses minimal profile by default - `stable` toolchain by default Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 weeks ago
Paul Balaji	7f3e0669d2	feat: add stride to relayed chains (#4716 ) ### Description - feat: add stride to relayer - feat: add stride to scraper ### Drive-by changes - fix filtering non-evm addresses in appFromAddressesMapHelper - fallback to manual `yarn install` in `yarn-build-with-cache` action - fix bug in app governor to make inevm env-test pass ### Related issues na ### Backward compatibility yes ### Testing manual --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Paul Balaji	2cc51c1640	chore: split cli e2e into separate job (#4733 ) ### Description chore: split cli e2e into separate job before: ![image](https://github.com/user-attachments/assets/bb19243f-fc38-478e-b94c-f39020756964) after: ![image](https://github.com/user-attachments/assets/6ebcb783-1d07-4350-8823-5cc5df7c5c65) ### Drive-by changes na ### Related issues `yarn-test` step sometimes taking even 15 mins nowadays, half of which is e2e tests ### Backward compatibility yes ### Testing ci	1 month ago
Lee	7bfc7ec81c	chore: remove old e2e cli tests (#4711 ) ### Description Removes the tests from workflow. We now use ts e2e tests ### Related issues - Fixes #4417	1 month ago
Paul Balaji	5f4540ed4e	fix: sort out codespell (#4679 ) ### Description fix: sort out codespell. Try using the official setup python action ### Drive-by changes na ### Related issues na ### Backward compatibility yes? ### Testing ci Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	1 month ago
Daniel Savu	2baaa11636	chore: disable sealevel e2e when possible (#4654 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Paul Balaji	d010772bb8	chore: delete test-skipped workflow (#4601 ) chore: delete test-skipped workflow - despite recent changes to improve filtering for MD files, our test/test-skipped triggers are still throwing up problems e.g. https://canary.discord.com/channels/935678348330434570/935678739663192184/1290706562796617728 - given a MD-only change is unlikely, and we're likely to have MD files for changesets more often than not, better to remove test-skipped altogether until it becomes essential to skip tests - given our CI has gotten cheaper+faster lately, not a huge overhead to run for MD-only changes	2 months ago
Yorke Rhodes	11a6a1cf2d	test: add olympix github action (#4354 ) ### Description Run olympix static analyzer --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Yorke Rhodes	05211a2e61	chore: update CODEOWNERS (#4555 ) ### Description Update CODEOWNERS	2 months ago
Paul Balaji	5ecc529e14	chore: tidy up worfklow triggers (#4479 ) chore: tidy up worfklow triggers This will hopefully stop the double triggering we're seeing currently for the X/X-skipped workflows rust.yml: - run if there are changes to rust dir or to the workflow file - always run in merge queue rust-skipped.yml: - only run if there are no changes to rust dir or to workflow file test.yml: - don't run if the only changes are MD files - always run in merge queue test.yml: - run if the only changes are MD files We always run the full rust.yml/test.yml workflows in the merge queue, because the path matching/filtering for push/pull_request isn't supported by the `merge_queue` argument. There's options to add a step to manually do it but considering our CI is a bit faster now it should be fine in the general case	2 months ago
Trevor Porter	cd13f6c08f	fix: fix VERGEN_GIT_SHA population in Docker image (#4503 ) ### Description Was accidentally removed in #4438. Wonder if there's an easy way to have tests fail if this doesn't work? ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Paul Balaji	1ab8751afb	fix: docker agent build (#4481 ) fix: docker agent build - update image from 1.72.1 -> 1.80.1 drive-by: update more `rust/` --> `rust/main/` drive-by: consolidate e2e non-cosmwasm cache, multiple cache steps per job can get in the way of each other --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	2 months ago
Mantas-M	096aeff13e	feat: Splitting `rust` workspace into `main` and `sealevel` (#4438 ) ### Description The single rust workspace has been split into 2 workspaces. The sealevel workspace includes the contents of the previous `sealevel` folder and the main workspace includes everything else. The workspaces differ in rust versions as the sealevel has the old one to ensure compatability, the main workspace has and updated `rustc` version of `1.80.1`. Some dependencies and sub-dependencies have been locked in versions of the old pre-split workspace to ensure no breaking code changes. The rust CI workflow has been updated to include both workspaces in the tests. ### Drive-by changes N/A ### Related issues Relates to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4361 ### Backward compatibility No. ### Testing Rust Unit tests from the CI	2 months ago
Paul Balaji	085e7d0463	feat: migrate large runners to buildjet (#4424 ) feat: migrate large runners to buildjet - includes migration to buildjet's cache - benefits: https://buildjet.com/for-github-actions/blog/launch-buildjet-cache#buildjet-cache-benefits - 20GB/week free cache is 2x what GHA provides - drive-by: add restore-keys for the yarn caches - more buildjet investigation notes [here](https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4445)	3 months ago
Paul Balaji	b91e0f446a	feat: remove extraneous caching (#4469 ) feat: remove yarn build cache - saves 600MB of cache space PER COMMIT - doesn't impact overall per-commit CI time - better CI time in the general case due to fewer cache evictions on the e2e matrix job - [with caching](https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10797745470) vs [no caching](https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10797213927?pr=4469) drive-by: disable docker caching for agent build - currently cache has no impact on build time of the agent image - rerunning builds for a commit or pushing empty commits should in theory lead to quicker builds with layer caching, but the main problem is that the `RUN` step of building the agents is not cached by the docker action - only RUNs with bind mounts get a checksum computed [(reference)](https://docs.docker.com/build/cache/invalidation/#general-rules) - disabling docker build caching could help save a bunch of cache space - best way to 4x speed here is moving this job to a buildjet 8vcpu runner (read [here](https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4445) for more info) drive-by: TLC - update to latest docker build action - provides a nice build summary and can generate artifacts that help break down where build time is spent - update check-env before build, given the current deprecation annotations - https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ - coverage step doesn't need to wait for `yarn-test` anymore	3 months ago
Paul Balaji	b94a74534d	chore: tidy up cli-advanced-e2e workflow (#4460 ) chore: tidy up cli-advanced-e2e workflow - we don't run agents in the cli-advanced-e2e test anymore since our push for the updated CLI v4 - until we add agents back (https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4070) or migrate these tests entirely (https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4417), we should simplify the test - stop the agent prebuild to save precious cache space + ci cost - reduces ci cost by switching simple ts tests to a standard github runner	3 months ago
Paul Balaji	15c1e3ba9e	chore: increase env-test timeout to 10 minutes (#4433 ) chore: increase env-test timeout to 10 minutes - to give even more headroom in case some tests take longer - trying to rule out chance of timeouts affecting the success/failure of a test https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10704561765/job/29678091884?pr=4395#step:6:1210	3 months ago
Paul Balaji	88589eb2a3	fix: use known safe multisend addresses in getSafe (#4415 ) - fix: use known safe addresses in getSafe - also requires updating the MultiSend governor helper to handle cases where there is no known `MultiSend` contract - hardcodes the `safeDeploymentsVersions` mapping, as it's not exposed by the safe protocol-kit - introduce utilities in the MultiSend to delete specific or all pending transactions - add helper scripts for safe tx delete operations --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	3 months ago
Mohammed Hussan	40974c7ec5	feat(envTests): Support using secret rpcs for CI env tests (#4408 ) ### Description - Use Arbitrum and Optimism private RPCs that are set in Github Secrets for env-test - Increase env-test timeout to 4 mins for viction - Adapt fork script so that it create anvil instance by calling a script ### Testing Manual	3 months ago
Paul Balaji	f30ba0efa4	fix: increase wait time for postgres to be ready in cosmos e2e (#4411 ) ## fix: increase wait time for postgres to be ready in cosmos e2e increase time waiting for postgres to be ready, to reduce this sort of flake https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10665491633/job/29559169324?pr=4410#step:13:2998 based on the logs it looks like 10s is just on the border, adding an extra 5s to give headroom ## drive-by fix: disable fail-fast on e2e-matrix currently only the non-cosmwasm tests are required to merge, therefore we should not fail the entire matrix if the cosmos job fails. This also means we can test that the issues we're seeing with the `cosmwasm` job do not affect the `non-cosmwasm` one.	3 months ago
Daniel Savu	dac2fb5210	feat: SOL (solana <> eclipse) warp route (#4268 ) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: Trevor Porter <tkporter4@gmail.com>	3 months ago
Danil Nemirovsky	d1bf212bf7	feat: Report git commit hash as agent metadata (#4282 ) ### Description * We are storing git commit hash as an environment variable when we compile the source code of an agent. * Validator uses git commit hash as a agent version in `metadata_latest.json` file. * File `metadata_latest.json` is overwritten every time when validator is restarted. * Git commit hash is extracted by `git` util, so, it should be available during build time. * If the directory with the source code does not contain `.git` folder, git commit hash will be defaulted to `VERGEN_IDEMPOTENT_OUTPUT`. Agent Metadata is propagated to Relayer and Scraper, but is not used there. We can use it in the future, reporting git hash commit in the logs, for example. ### Backward compatibility Yes ### Testing * Tested locally with E2E Tests. * Tested against S3 by deploying docker image into k8s --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	4 months ago
Danil Nemirovsky	c176e16286	docs: Add jq as prerequisite since yarn install won't work without it (#4262 ) ### Description Adds `jq` as prerequisite in README.md since `yarn install` won't work without it. ### Testing Checked how README.md looks in GitHub. --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>	4 months ago
Daniel Savu	4fa75a4bd8	chore: better agent e2e test naming (#4157 ) ### Description For partners / OSS contributors to have an easier time building and testing the env most relevant to them	4 months ago
Paul Balaji	4f1ea15e28	chore: set env-test timeout (#4120 ) - chore: set env-test timeout - to avoid machines spinning idly for hours/days in jobs like this https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/9872063807/job/27261501530?pr=3888#step:6:44 --------- Signed-off-by: pbio <10051819+paulbalaji@users.noreply.github.com>	4 months ago
Paul Balaji	653bbcff52	fix(e2e): hardcode kathy chains for e2e in send-test-messages.ts (#4067 ) resolves https://github.com/hyperlane-xyz/issues/issues/1291 - remove test4 from kathy test - drive-by tidy-up of `test4` metadata - resets e2e test timeout back to original figure - reuse original e2e rust cache gonna keep the original commits on here as a trail of thought --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	d51813a1da	bump E2E_CI_TIMEOUT_SEC on non-cosmwasm test to 1hr Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	a23cf6420c	tidy up test.yml branch triggers Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	cf253328a0	Update e2e-non-cosmwasm ci timeout	5 months ago
Paul Balaji	45dc4f99c9	use clean rust cache for e2e	5 months ago
Paul Balaji	b99920ecca	fix(ci): use the correct commit sha for agent/monorepo image tags (#4052 ) - use the correct commit hash for the agent and monorepo image tag - the actual checked out commit was correct, but this now ensures that the TAG_SHA matches the checked out commit hash - drive-by ensure that workflow gets triggered on changes to itself --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	cc0ea73360	feat: pin monorepo to a specific registry version (#4041 ) - feat: pin monorepo to a specific registry version (cherry-pick #4031) - drive-by agent config update --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	1876f68127	feat: pin monorepo to a specific registry version (#4031 ) feat: pin monorepo to a specific registry version - introducing a `.registryrc`, which can be a commit hash, branch or tag - introduce a new action just for checking out a registry - remove registry caching because it's quicker now to just checkout the specified version --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	18056aafdd	chore(ci): fix ci workflow filters on main (#4022 ) chore(ci): fix ci workflow filters on main generally copying the path/filters for `pull_request` into `push` so that we correctly run the right workflows --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Paul Balaji	39f66df326	feat(ci): rust caching in `test` workflow (#4021 ) - brings https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4015 to cli-2.0 branch - cherry-pick e2e flake fix - ensure tests run on pushes to `cli-2.0` --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>	5 months ago
Paul Balaji	0d12ff31cd	feat(ci): rust caching in `test` workflow (#4015 ) - draft: improve rust target caching in ci - separate caches for e2e-cosmwasm, e2e-noncosmwasm, cli-e2e test - drive-by adding `restore-keys` test expectation: - 1st commit of rust changes will take the full required time as it'll have to do a fresh build and then cache - subsequent builds of a particular rust change will be faster because it'll pickup the rust cache from before --------- Signed-off-by: Paul Balaji <10051819+paulbalaji@users.noreply.github.com>	5 months ago
Noah Bayindirli 🥂	bd3ca9195a	chore(cli): update ci-test to ci-advanced-test (#4011 ) ### Description - updates `ci-test.sh` name to `ci-advanced-test.sh` ### Drive-by changes - none ### Related issues - fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3995 ### Backward compatibility - yes ### Testing - implicit	5 months ago
Paul Balaji	b0828b3d0e	feat: reintroduce `ism read` and `hook read` commands (#3990 ) the original functionality of these commands got lost across a couple of refactors 1. `ism read`/`hook read` was merged to become `core read`, which still had the purpose of "gimme config at this address" 2. then with a recent change, `core read` became "gimme the ism/hook configs relating to this mailbox address" This PR adds the original functionality back of returning the ISM/Hook configs for any ISM/Hook address (on EVM) drive-by: - update mainnet config - fix typescript linting errors/warnings	5 months ago
Paul Balaji	5cc64eb095	feat: deploy to new chains (fraxtal, linea, sei) (#3887 ) https://github.com/hyperlane-xyz/issues/issues/1279 - adds `fraxtal`, `linea`, `sei` - supports `osmosis` as a remote - ~drive-by hack to skip reconfiguring the same gas oracle (cc @tkporter)~ - drive-by fix to bring the logic of estimating tx + adding 10% buffer into the ism factory (as originally seen in the multiprovider handleDeploy function) - drive-by fix for creating custom safes - drive-by support of `osmosis` as a remote chain - drive-by addition of `osmosis` to the rust agent --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: nambrot <nambrot@googlemail.com>	5 months ago
Paul Balaji	9f19cdf469	ci: update action versions (#3927 ) - update to latest versions of actions - notably docker tasks get a couple of major bumps - rename the foundry action to its current name --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	b0d26b66e4	fix: test filtering for `.md` changes (#3936 ) fix: test filtering for `.md` changes - fix the rust-skipped flow - add a test-skipped flow to still go green on the required status checks --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	47831d5211	ci: ignore `*.md` changes when triggering rust/test workflows (#3930 ) - skips unnecessary tests for PRs on just markdown changes e.g. README Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	50d2f29324	ci: configure merge queue for `main` (#3913 ) - configure the rust/test workflows to support merge queues into `main` --------- Signed-off-by: Paul Balaji <paul@hyperlane.xyz>	6 months ago
Paul Balaji	c38f799afa	ci: cherry-pick merge queue update (#3914 ) bringing over https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/3913	6 months ago
Yorke Rhodes	876e1cf928	chore: run cli-e2e on cli-2.0 branch (#3864 )	6 months ago
Yorke Rhodes	49f41d9759	chore: Merge branch 'main' into cli-2.0 (#3863 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Kunal Arora <55632507+aroralanuk@users.noreply.github.com> Co-authored-by: Connor McEwen <connor.mcewen@gmail.com> Co-authored-by: Trevor Porter <tkporter4@gmail.com> Co-authored-by: byeongsu-hong <hong@byeongsu.dev> Co-authored-by: Avi Atkin <103125634+avious00@users.noreply.github.com> Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com> Co-authored-by: J M Rossy <jm.rossy@gmail.com> Co-authored-by: Ali Alaoui <aalaoui2001@gmail.com> Co-authored-by: Nam Chu Hoai <nambrot@googlemail.com> Co-authored-by: Paul Balaji <paul@hyperlane.xyz> Co-authored-by: omahs <73983677+omahs@users.noreply.github.com>	6 months ago
Nam Chu Hoai	f2dc925cb3	Remove nambrot from codeowners (#3846 ) It had to happen #RIP, my getting review requested ended up too noisy to miss actual tags in issues	6 months ago
Trevor Porter	fdd1421540	fix: fetch the registry's `main` branch in the monorepo Docker image (#3841 ) ### Description Infra services require the presence of a registry. This is expected to be found at the env var REGISTRY_URI. This PR fetches the latest registry from `main` and uses that as the registry in the monorepo image for infra services / scripts to make use of. To prevent caching of this git clone, we use a build-time arg such that if the arg changes, any later layers in the image will be ran. See https://stackoverflow.com/a/73501716 ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues - Partially fixes https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3827 - we'll need a deploy to fully close it out ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->	6 months ago

1 2 3 4 5

240 Commits (8417abf1427bc81fb4ff17cabcc0df352c9c6065)