-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
applications: Fixed assert on Matter bridge #18113
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 2ab06f02f7de87b7e708fb912e909d5925110e73 more detailssdk-nrf:
Github labels
List of changed files detected by CI (6)
Outputs:ToolchainVersion: 3dd8985b56 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
applications/matter_bridge/src/simulated_providers/simulated_humidity_sensor_data_provider.cpp
Outdated
Show resolved
Hide resolved
applications/matter_bridge/src/simulated_providers/simulated_humidity_sensor_data_provider.cpp
Outdated
Show resolved
Hide resolved
...cations/matter_bridge/src/simulated_providers/simulated_temperature_sensor_data_provider.cpp
Outdated
Show resolved
Hide resolved
After the last Zephyr up-merge, getting rand number from the timer callback leads to the crypto assert. Added scheduling rand operation to the application event. Signed-off-by: Kamil Kasperczyk <[email protected]>
df87d74
to
2ab06f0
Compare
After the last Zephyr up-merge, getting rand number from the timer callback leads to the crypto assert.
Added scheduling rand operation to the application event.