Guard estimatedCompletion against division-by-zero in IndexerService replay progress in src/indexer/service.ts

[Jagadeeshftw]

📌 Description

In src/indexer/service.ts, the replay progress reporting computes an estimated completion using a throughput rate. On the first progress tick (or when no rows have yet been replayed) the divisor can be zero, producing Infinity/NaN for estimatedCompletion, which then propagates into logs/metrics and any progress endpoint.

💡 Why it matters: NaN/Infinity ETAs corrupt dashboards and can break JSON serialization of progress; the estimate must degrade gracefully.

🧩 Requirements and context

• Guard the estimatedCompletion computation against zero/negative rate and zero elapsed time.
• Return null/omit the estimate when it cannot be computed instead of NaN/Infinity.
• Ensure any progress metric/log handles the null case cleanly.
• Add unit tests for the first-tick and zero-rate scenarios.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b fix/indexer-eta-divzero

2. Implement changes

• Write/modify the relevant source: src/indexer/service.ts
• Write comprehensive tests: tests/indexer-replay.test.ts
• Add documentation: inline TSDoc on the estimate semantics
• Include TSDoc doc comments
• Validate security assumptions: no invalid numbers in serialized output

3. Test and commit

• Run tests:

npm test

• Cover edge cases: zero rows replayed, zero elapsed, normal progress
• Include test output and security notes in the PR description.

Example commit message

fix(indexer): guard replay ETA against division by zero

✅ Acceptance criteria

• No NaN/Infinity in estimatedCompletion
• Estimate is null/omitted when uncomputable
• Logs/metrics handle the null case
• Tests cover first-tick/zero-rate

🔒 Security notes

Ensure invalid numeric values cannot break JSON responses consumed by clients.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Pascdav001]

@Pascdav001 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello boss, Please assign this issue to me. i checked it out and im confident i will solve it
my eta is 4 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Pascdav001 to this issue.

[drips-wave]

Congratulations, @Pascdav001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Pascdav001: 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 🌊