-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Lora timer cancellation #14422
Fix Lora timer cancellation #14422
Conversation
This function must be called by the callback registered in init. It clears the timer_id to prevent abusive use of the stop methods on expired timer.
@pan-, thank you for your changes. |
I'll fire up a set of devices for testing and let it run over the weekend. I should be able to spare at least 10 devices. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll edit the file to add a new line to get this into CI now
CI started |
Please review unittests failures (related to the changes) |
Jenkins CI Test : ❌ FAILEDBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would class this as an bugfix - not a feature update.
Pull request has been modified.
@0xc0170 Fixed, I change the PR qualification as bug fix: The API added is internal to the stack. |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
Fix abusive use of
LoRaWANTimer::stop
. Events were canceled even when they were being executed or after their execution.This change reset the event ID to 0 before calling the callback.
A new API has been added to achieve this task:
LoRaWANTimer::clear
Documentation
None
Pull request type
Test results
Reviewers
@Swap-File