chore: remove misleading error log

[0xstepit]

Summary by CodeRabbit

• Chores
  • Removed error logging statements from dispatcher functions. System behavior remains unchanged; failed retrievals continue to default to zero/empty values as before.

[coderabbitai]

Walkthrough

Removed error logging statements from GetDispatchedAmount and GetDispatchedCounts functions. Both functions now silently default to zero/empty values when retrieval fails, eliminating debug output while preserving existing control flow behavior.

Changes

Cohort / File(s)	Summary
Error logging removal keeper/component/dispatcher/state.go	Removed logger error statements from GetDispatchedAmount and GetDispatchedCounts error paths; functions now return default values without emitting debug logs

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file with straightforward removal of logging calls
• No logic changes or control flow modifications
• No public API or signature alterations

Poem

🐰 Quiet whispers fade away,
No more logs to clutter the day,
Zero flows with silent grace,
Clean and swift—just empty space!
✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: remove misleading error log' accurately reflects the main change: removing error logging statements that were misleading in the dispatcher state code.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch stepit/remove-logs

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1108a2 and 7f0bf2c.

📒 Files selected for processing (1)

• keeper/component/dispatcher/state.go (0 hunks)

💤 Files with no reviewable changes (1)

• keeper/component/dispatcher/state.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: prepare
• GitHub Check: build
• GitHub Check: unit-test
• GitHub Check: lint

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}