Repository navigation
indexer: poller.ts has no retry/backoff around fetchPage/ingestPage failures #569
Description
Activity
@olubukolatanko209-doc has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi Maintainer, I’m familiar with this issue and can implement a fix. Please assign it to me if possible.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @olubukolatanko209-doc to this issue.
@Aisha000-0 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
hello maintainer i can fix this issue. kindly assign
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Aisha000-0 to this issue.
@kolawoleoluwaferanmi014-a11y has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello Maintainer, I’ve thoroughly read through the issue description and understand the expected outcome. I’m confident I can take this from implementation through testing and deliver a solution that meets the acceptance criteria. I’d appreciate the opportunity to work on it.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @kolawoleoluwaferanmi014-a11y to this issue.
@arraahmon244-pixel has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I want to work in this, it is my work
ℹ️ Repo Maintainers: To accept this application, review their application or assign @arraahmon244-pixel to this issue.
@Peculiarr7 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi! I’m a full-stack developer with a strong blockchain background, and I’m confident I can resolve this issue quickly and effectively. I’ll deliver a clean, reliable solution with immediate attention to detail, ensuring it’s completed as soon as possible. Please assign it to me—I’m ready to get started right away.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peculiarr7 to this issue.
@markdavid000 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello maintainer, I can handle this issiue.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @markdavid000 to this issue.
Congratulations, @markdavid000! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @markdavid000: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
🎉 This issue has been marked as completed on GrantFox!
@markdavid000's PR #738 was approved and merged by @Jaydbrown.
🏆 @markdavid000: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (223 total points). Track your full progress on GrantFox.
👏 Great work, @markdavid000! Keep contributing to conduit-protocol.
- added a commit that references this issue
on Oct 6, 2026
A transient RPC error or a Postgres connection blip during
poller.ts's read-fetch-ingest-save loop has no visible retry or backoff strategy in the current 105-line implementation. Depending on what happens on an unhandled rejection in the loop, the worker either crashes (fine, if something restarts it) or silently stalls (not fine) — this needs to be pinned down and tested either way.Acceptance criteria: add explicit retry-with-backoff around the RPC fetch step, and a test asserting the poller doesn't silently stop advancing after a single transient failure.