[management] fix utc difference on last seen status for a peer#5348
[management] fix utc difference on last seen status for a peer#5348
Conversation
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughWalkthroughIntroduces Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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 |
|
There was a problem hiding this comment.
Pull request overview
This PR fixes a UTC timezone inconsistency bug in peer "last seen" timestamp tracking. The issue occurred when the sync timestamp wasn't converted to UTC before being passed to downstream functions that perform timestamp comparisons with stored peer status data.
Changes:
- Introduced
syncStartvariable by convertingreqStartto UTC in theSyncfunction - Replaced
reqStartwithsyncStartin all calls that pass timestamps for peer status tracking - Preserved
reqStartfor local timing measurements (metrics and logging)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.



Describe your changes
Issue ticket number and link
Stack
Checklist
Documentation
Select exactly one:
bug fix
Docs PR URL (required if "docs added" is checked)
Paste the PR link from https://github.com/netbirdio/docs here:
https://github.com/netbirdio/docs/pull/__
Summary by CodeRabbit