You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #20134 and #20164 together introduced a storage API compliance audit.
This audit must be run and pass on nRF Connect and succeed against PersistentStorageDelegate used by lock-app (KVS file based)
To run the audit for anything using Server, build your target with chip_support_enable_storage_api_audit=true added to your GN args and then run your binary in a debugger. The default audit is added to Server::Init() and will cause an assert with logs on failure.
Audit passes once you see the following string in your logs
==== PersistentStorageDelegate API audit: SUCCESS ====
On failure, informative assertion failures are logged to assist in debugging.
Proposed Solution
Build with audit enabled
Run and comment on passing along with the SHA of the commit where it was run. Provide a logs capture of your run.
If you find failures, please document them in comments on the issue to help SDK team audit the types of failures/assumptions made.
Close the issue once you pass
The text was updated successfully, but these errors were encountered:
Problem
PR #20134 and #20164 together introduced a storage API compliance audit.
This audit must be run and pass on nRF Connect and succeed against PersistentStorageDelegate used by lock-app (KVS file based)
To run the audit for anything using Server, build your target with
chip_support_enable_storage_api_audit=true
added to your GN args and then run your binary in a debugger. The default audit is added to Server::Init() and will cause an assert with logs on failure.Audit passes once you see the following string in your logs
==== PersistentStorageDelegate API audit: SUCCESS ====
On failure, informative assertion failures are logged to assist in debugging.
Proposed Solution
The text was updated successfully, but these errors were encountered: