feat: add geyser plugin safe-start checks#6
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-019db3d7-0da5-76ce-a24b-dc7507211386 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3d7-0da5-76ce-a24b-dc7507211386 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3d7-0da5-76ce-a24b-dc7507211386 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3d7-0da5-76ce-a24b-dc7507211386 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3d7-0da5-76ce-a24b-dc7507211386 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3df-499e-72bd-9be0-df089c30106d Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019db3e1-8171-7040-8bbc-a8f061eb1b72 Co-authored-by: Amp <amp@ampcode.com>
* master: fix: stabilize geyser plugin startup (#4)
Amp-Thread-ID: https://ampcode.com/threads/T-019dd297-daf4-7092-91a6-1681a0d669ee Co-authored-by: Amp <amp@ampcode.com>
Step 2: Drop the unused allowed field from the ClientCheckpoint struct and update all four scenario files to stop constructing it: - ix-tests/src/expectation.rs: Removed allowed field from struct - ix-tests/src/scenarios/single_basic.rs: Updated lamport_client_checkpoint helper and owner_data_checkpoint block - ix-tests/src/scenarios/dual_concurrent.rs: Updated single_update_checkpoint helper - ix-tests/src/scenarios/dual_restart.rs: Updated repeated_checkpoint and empty_checkpoints helpers - ix-tests/src/scenarios/single_load.rs: Removed allowed from construction All ix-tests unit tests pass. Clippy errors in expectation.rs were auto-fixed (collapsible_if). Amp-Thread-ID: https://ampcode.com/threads/T-019dd298-cc3a-716f-a374-2375f3a99bf0 Co-authored-by: Amp <amp@ampcode.com>
The checkpoint runner re-evaluated every required entry against the full observation snapshot on each loop iteration. Required entries that had already been satisfied were re-checked against the same observations every tick, and a single observation could be counted toward multiple distinct required entries. Track per-client matching state across loop iterations so that: - each required entry, once matched, stays matched and is not re-evaluated; - each loop iteration only scans observations that arrived since the last poll; - each observation can only consume a single required entry. Replace the previous unmatched_required helper with a stateful consume_observations helper and update unit tests to cover the new incremental, consuming behavior. Amp-Thread-ID: https://ampcode.com/threads/T-019dd29f-8b80-76bf-8a1f-623f120781d8 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019de28c-6339-7789-b2b9-91574b2fb9dc Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019de28e-1889-70e1-8acd-8644a015c46e Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019df7b6-44aa-768c-818c-87ade4cf3e44 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019df7da-5102-7128-baa4-52698cee5051 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e1b5e-3180-777e-9969-0d19e019fb98 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e1b63-c250-70ac-ab23-54c5a641b8ea Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e1b68-4183-759b-8b06-bb7473bba060 Co-authored-by: Amp <amp@ampcode.com>
* master: feat: add ix integration test suite (#5)
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (13)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Summary
Adds safe-start startup checks for the geyser plugin so validator/plugin startup fails early with actionable errors instead of continuing into harder-to-debug runtime failures.
Details
geyser-plugin
grpc-service