[BLE] Fixed inconsistent casing issue for SecurityDb #6494
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
|
/morph build |
1 similar comment
|
/morph build |
Build : SUCCESSBuild number : 1615 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1244 |
Test : FAILUREBuild number : 1397 |
|
/morph test |
Test : SUCCESSBuild number : 1405 |
theotherjimmy
added
ready for merge
release-version: 5.8.2
and removed
needs: CI
labels
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.
Description
Fix for #6476.
The SecurityDb/MemorySecurityDb had some casing inconsistencies across the BLE security manager implementation which created some compilation issues when compiling from a case-sensitive filesystem.
This PR fixes these inconsistencies.
Pull request type
[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change