Handle insert error

[rockinrimmer]

This re-adds pageviews to the queue if there is an error inserting into Clickhouse.

Summary by CodeRabbit

• Bug Fixes
  • Enhanced page view queue error handling to preserve and retry failed batches, with improved error messages showing the count of affected items.

[vercel]

@rockinrimmer is attempting to deploy a commit to the goldflag's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Enhanced error handling in the pageviewQueue service. When processing fails, the failed batch is now re-queued at the beginning of the queue with improved logging that indicates how many items are being re-queued.

Changes

Cohort / File(s)	Summary
Queue error recovery enhancement server/src/services/tracker/pageviewQueue.ts	Improved catch block in processQueue to re-queue failed batches using unshift() and log descriptive messages including item counts

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify that unshift() correctly places the batch at the front of the queue for retry
• Confirm the logging message accurately reflects the batch size
• Ensure error recovery doesn't cause infinite loops or memory issues with retries

Poem

🐰 A queue once lost its way when errors came,
But now we've added magic—retry with a name!
We unshift with care, log each failed plight,
The batch hops back up, ready to fight! 🚀

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 ba9a3a7 and 7089efe.

📒 Files selected for processing (1)

• server/src/services/tracker/pageviewQueue.ts (1 hunks)

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.}