hyperlane-monorepo

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

blockchain hyperlane interchain monorepo

History

Trevor Porter 9a83eb4d57 Sequence-aware indexing refactor (#3262 ) ### Description Part 1 of an indexing refactor. This mostly focuses on the sequence-aware cursors. Changes: - Some renames, e.g. `SequenceIndexer` -> `SequenceAwareIndexer`, `sequence_and_tip` -> `latest_sequence_count_and_tip` - Moved cursors out of `contract_sync/cursor.rs` into `contract_sync/cursors/*` - The goal was to make the the Forward sequence-aware cursor, the Backward sequence-aware, and the ForwardBackward sequence aware cursors more resilient, easier to understand, and better tested. - General strategy for doing this was to: - Only move onto a new range to index if the logs passed into the cursor's `update` function justify this - If updated with any weird data, like gaps in logs, rewind the cursor and retry previously queried ranges I'd recommend starting the review in the following order: 1. `rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/forward.rs` - where `ForwardSequenceAwareSyncCursor` & tests live 2. `rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/backward.rs` - where `BackwardSequenceAwareSyncCursor` & tests live 3. `rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/mod.rs` - where `ForwardBackwardSequenceAwareSyncCursor` lives ### 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 -->	9 months ago
..
src	Sequence-aware indexing refactor (#3262 )	9 months ago
Cargo.toml	Deploy injective and inEVM (#3140 )	10 months ago

Sequence-aware indexing refactor (#3262 )

### Description

Part 1 of an indexing refactor. This mostly focuses on the
sequence-aware cursors.

Changes:
- Some renames, e.g. `SequenceIndexer` -> `SequenceAwareIndexer`,
`sequence_and_tip` -> `latest_sequence_count_and_tip`
- Moved cursors out of `contract_sync/cursor.rs` into
`contract_sync/cursors/*`
- The goal was to make the the Forward sequence-aware cursor, the
Backward sequence-aware, and the ForwardBackward sequence aware cursors
more resilient, easier to understand, and better tested.
- General strategy for doing this was to:
- Only move onto a new range to index if the logs passed into the
cursor's `update` function justify this
- If updated with any weird data, like gaps in logs, rewind the cursor
and retry previously queried ranges

I'd recommend starting the review in the following order:

1.
`rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/forward.rs`
- where `ForwardSequenceAwareSyncCursor` & tests live
2.
`rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/backward.rs`
- where `BackwardSequenceAwareSyncCursor` & tests live
3. `rust/hyperlane-base/src/contract_sync/cursors/sequence_aware/mod.rs`
- where `ForwardBackwardSequenceAwareSyncCursor` lives

### 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
-->

9 months ago

src

Sequence-aware indexing refactor (#3262 )

9 months ago

Cargo.toml

Deploy injective and inEVM (#3140 )

10 months ago