Fix MISRA rule 3.1 violations #9068
Merged
Conversation
This file contains hidden or 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
holtrop
force-pushed
the
fix-misra-3.1-violations
branch
from
fee4b28 to
33d0e1e
Compare
Author
|
retest this please (AgentOfflineException) |
Contributor
|
Interesting; I suspect this is no longer allowed for new code? I bumped into this just today. |
douzzer
approved these changes
Aug 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Description
This was another low-hanging fruit to remove MISRA rule 3.1 violations ("The character sequences /* and // shall not be used within a comment.")
Testing
Unit and CI tests.
Checklist