Merge bitcoin/bitcoin#26302: refactor: Use type-safe time point for CWallet::m_next_resend#1224
Conversation
Backport of bitcoin#26302 Co-authored-by: MacroFake <falke.marco@gmail.com>
|
Warning Rate limit exceeded@DashCoreAutoGuix has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 2 seconds before requesting another review. ⌛ 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. 📒 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 |
Backports bitcoin#26302
Original commit: 50cc8ef
Changes
NodeClock::now()instead ofGetTime()for type safetym_next_resendfromstd::atomic<int64_t>tostd::atomic<NodeClock::time_point>FastRandomContext{}.rand_uniform_delay()for type-safe random delay#include <util/time.h>to wallet.hDash-specific adaptations
std::atomicwrapper aroundm_next_resend(Dash uses atomic for thread safety).load()calls for atomic access in comparisonsOriginal PR description
GetTimeis not type-safe, thus deprecated.ACKs for top commit:
shaavan: Code Review ACK fa51cc9
aureleoules: ACK fa51cc9