hyperlane-monorepo

The home for Hyperlane core contracts, sdk packages, and other infrastructure

blockchain hyperlane interchain monorepo

History

Trevor Porter 57bbb16cc1 feat: panics upon startup when RPC issues occur include the offending chain (#4323 ) ### Description Some quick low hanging fruit to make debugging easier in the future. Today (https://discord.com/channels/935678348330434570/1273582453889699843) some chains were having RPC issues and it caused an agent deploy to panic upon startup. Debugging this was hard because the panic message just indicates an error is occurring, but doesn't say what the offending chain is! Examples: - https://cloudlogging.app.goo.gl/puQk7hm4fXyJhYKs8 - https://cloudlogging.app.goo.gl/5qZrbc2Ww4LWQXWC6 - https://cloudlogging.app.goo.gl/ZL7mKbBzzJaePtty9 All these panic happen when constructing the cursor, which isn't yet done in an indexing task. The quick and easy fix is to just use expect instead of unwrap We still unwrap in a few places, but mostly in places that aren't susceptible to flaky RPC issues, e.g. reading from a HashMap that we know should always have an entry, etc ### 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 -->		4 months ago
..
migration	feat: add arbitrumsepolia, basesepolia, ecotestnet, optimismsepolia, polygonamoy to core chains (#4297 )	4 months ago
src	feat: panics upon startup when RPC issues occur include the offending chain (#4323 )	4 months ago
Cargo.toml	feat: Relayer tokio task instrumentation (#3760 )	6 months ago
README.md	Message explorer entities (#998 )	2 years ago

README.md

For local testing, setup a postgres database with

docker run --name scraper -e POSTGRES_PASSWORD=47221c18c610 -p 5432:5432 -d postgres

# optionally to connect
docker exec -it scraper /usr/bin/psql -U postgres

# and to shutdown
docker stop scraper
docker rm -v scraper

To init the database, run from rust dir

cargo run --package migration --bin init-db

To re-create the database, run from rust dir

cargo run --package migration --bin recreate-db

To re-generate the sea-orm entity code, when no database is running in docker and from the rust dir, run

cargo run --package migration --bin generate-entities

Note: This will install sea-orm-cli, start a docker container for postgresql, and then replace the existing entities. It will not work if docker is not setup or if anything is already bound on port 5432.