fix: use timezone-aware datetime in bundle export metadata and stats - #2
fix: use timezone-aware datetime in bundle export metadata and stats#2saurabhhhcodes wants to merge 2 commits into
Conversation
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
🔍 PR Code Graph Analysisfix: use timezone-aware datetime in bundle export metadata and stats (#2) 📊 Interactive VisualizationView the blast radius graph: PR Reviewer Dashboard 📦 ArtifactsThe graph JSON has been uploaded as a build artifact: Generated by CodeGraphContext using FalkorDB Lite |
Bugs Fixed:
Naive datetime in _extract_metadata (cgc_bundle.py:287): Used datetime.now() without timezone, creating offset-naive timestamps inconsistent with the rest of the codebase. Fixed to datetime.now(timezone.utc).
Naive datetime in _generate_stats (cgc_bundle.py:602): Same issue with generated_at timestamp. Fixed to datetime.now(timezone.utc) and added timezone to the module-level import.