-
Notifications
You must be signed in to change notification settings - Fork 7
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
🎨 (rc): Call process_event of State Machine in event queue #635
Merged
ladislas
merged 1 commit into
develop
from
ladislas/yann/feature/state-machine/call-raise-in-event-queue
Mar 25, 2022
Merged
🎨 (rc): Call process_event of State Machine in event queue #635
ladislas
merged 1 commit into
develop
from
ladislas/yann/feature/state-machine/call-raise-in-event-queue
Mar 25, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## develop #635 +/- ##
========================================
Coverage 99.01% 99.01%
========================================
Files 89 89
Lines 1828 1830 +2
========================================
+ Hits 1810 1812 +2
Misses 18 18
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Kudos, SonarCloud Quality Gate passed! |
File comparision analysis report🔖 Info
Click to show memory sections
📝 SummaryClick to show summary
🗺️ Map files diff outputClick to show diff list
|
File comparision analysis report🔖 Info
Click to show memory sections
📝 SummaryClick to show summary
🗺️ Map files diff outputClick to show diff list
|
ladislas
deleted the
ladislas/yann/feature/state-machine/call-raise-in-event-queue
branch
March 25, 2022 13:26
ladislas
added a commit
that referenced
this pull request
Apr 28, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
ladislas
added a commit
that referenced
this pull request
May 4, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
ladislas
added a commit
that referenced
this pull request
May 4, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
ladislas
added a commit
that referenced
this pull request
May 9, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
ladislas
added a commit
that referenced
this pull request
May 11, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
ladislas
added a commit
that referenced
this pull request
May 11, 2022
When sending reinforcer (or any timed command) while still sending punctual commands resulted in deadlock because of ISR vs mutex lock priority issues (similar to #635) Solution was to add event queue in CommandKit to `execute` commands in a differrent context Co-Authored-By: Ladislas de Toldi <ladislas@detoldi.me>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.