-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy scraper with Sealevel chains like Solana / Eclipse #4274
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 11, 2024
### Description Enable Solana and Eclipse in Scraper. We don't relay messages in Solana and Eclipse testnets, so, we don't enable these testnets in Scraper. ### Related issues - Fixes #4274 ### Backward compatibility Yes ### Testing E2E Ethereum and Sealevel test Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
tiendn
pushed a commit
to tiendn/hyperlane-monorepo
that referenced
this issue
Jan 11, 2025
### Description Enable Solana and Eclipse in Scraper. We don't relay messages in Solana and Eclipse testnets, so, we don't enable these testnets in Scraper. ### Related issues - Fixes hyperlane-xyz#4274 ### Backward compatibility Yes ### Testing E2E Ethereum and Sealevel test Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
tiendn
pushed a commit
to tiendn/hyperlane-monorepo
that referenced
this issue
Jan 11, 2025
…yperlane-xyz#4986) ### Description Disable Eclipse in Scraper until we get archival RPC endpoint ### Related issues - Contributes into hyperlane-xyz#4274 ### Backward compatibility Yes ### Testing No testing since it is a config change --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
tiendn
pushed a commit
to tiendn/hyperlane-monorepo
that referenced
this issue
Jan 11, 2025
### Description Enable Solana and Eclipse in Scraper. We don't relay messages in Solana and Eclipse testnets, so, we don't enable these testnets in Scraper. ### Related issues - Fixes hyperlane-xyz#4274 ### Backward compatibility Yes ### Testing E2E Ethereum and Sealevel test Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
tiendn
pushed a commit
to tiendn/hyperlane-monorepo
that referenced
this issue
Jan 11, 2025
…yperlane-xyz#4986) ### Description Disable Eclipse in Scraper until we get archival RPC endpoint ### Related issues - Contributes into hyperlane-xyz#4274 ### Backward compatibility Yes ### Testing No testing since it is a config change --------- Co-authored-by: Danil Nemirovsky <4614623+ameten@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
blocked by: #4273
Rolling this out probably should involves similar steps as what's described here when rolling out Cosmos: #3356. maybe even at the same time?
We'll want to be cautious about this breaking prod services that depend on the scraper, e.g. the explorer UI, because this involves a DB schema change (e.g. #3331). Instead of rolling this out straight to prod on the existing scraper, I think it may be better to deploy this new scraper alongside the old one, with the intent of eventually shutting down the old scraper and moving over to this new one. This way we'll continue to have the explorer UI work well & give Rossy / others the opportunity to move over to this new DB. If we've already spun up a new scraper that works with Cosmos chains that isn't yet consumed by any services, we can just ship to that one, being cautious of any DB incompatibilities. Imo it's easier to avoid a data migration and just sync from scratch, but defer to whoever does this
The text was updated successfully, but these errors were encountered: