The previous implementation of the monotonic clock was subjected to time jumps, which caused issues when using the Countdown class. To address this, the monotonic clock is now based on the FreeRTOS tick count. Once the initial time is set, it ensures true monotonic behavior.
The previous implementation of the monotonic clock was subjected to time jumps, which caused issues when using the Countdown class. To address this, the monotonic clock is now based on the FreeRTOS tick count. Once the initial time is set, it ensures true monotonic behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The previous implementation of the monotonic clock was subjected to time jumps, which caused issues when using the Countdown class. To address this, the monotonic clock is now based on the FreeRTOS tick count. Once the initial time is set, it ensures true monotonic behavior.