only create activity events every 2 hours

[sawka]

No description provided.

[coderabbitai]

Walkthrough

The telemetry module's time rounding logic for activity events was modified in two functions. Both updateActivityTEvent and TruncateActivityTEventForShutdown now round timestamps to 2-hour boundaries instead of hourly boundaries. The rounding strategy remains consistent across both functions: truncate to the boundary, then add the interval duration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Description check	❓ Inconclusive	No description was provided by the author, which makes this check inconclusive as there is no content to evaluate.	Add a description explaining the rationale for changing from hourly to 2-hour activity event intervals.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: activity events are now created on a 2-hour interval instead of hourly.

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a07e078 and 757aa09.

📒 Files selected for processing (1)

• pkg/telemetry/telemetry.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). (3)

• GitHub Check: Analyze (go)
• GitHub Check: Build for TestDriver.ai
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

pkg/telemetry/telemetry.go (2)

198-198: LGTM! Consistent with updateActivityTEvent.

The 2-hour boundary logic matches the change in updateActivityTEvent, ensuring timestamp alignment is consistent across both normal updates and shutdown handling.

---

165-166: Code change is correct and consistent. Both updateActivityTEvent and TruncateActivityTEventForShutdown properly implement the 2-hour boundary logic with matching timestamp rounding. Existing 1-hour boundary events will be retained until removed by the age-based cleanup logic, which is expected behavior for this intentional transition.

---

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