Use UUID v4 instead of v1 for RunID and outbox event IDs#184
Use UUID v4 instead of v1 for RunID and outbox event IDs#184andrewwormald merged 1 commit intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
|



Problem
uuid.NewUUID()generates UUID v1 (time+MAC-based), but the docs state RunID is UUID v4. V1 leaks the host MAC address in containerized environments.Why
Documentation says v4, code produces v1. V1 embeds infrastructure info that shouldn't be exposed.
Fix
Switch to
uuid.NewRandom()(v4) intrigger.goandevent.go.🤖 Generated with Claude Code