Skip to content
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

Restyle Change persistent storage SyncGetKeyValue API to match constraints of KvsStorageManager #20186

Conversation

restyled-io[bot]
Copy link
Contributor

@restyled-io restyled-io bot commented Jun 30, 2022

A duplicate of #20164 with additional commits that automatically address
incorrect style, created by Restyled.

⚠️ Even though this PR is not a Fork, it contains outside contributions.
Please review accordingly.

Since the original Pull Request was opened as a fork in a contributor's
repository, we are unable to create a Pull Request branching from it with only
the style fixes.

The following Restylers made fixes:

To incorporate these changes, you can either:

  1. Merge this Pull Request instead of the original, or

  2. Ask your contributor to locally incorporate these commits and push them to
    the original Pull Request

    Expand for example instructions
    ```console
    git remote add upstream https://github.com/project-chip/connectedhomeip.git
    git fetch upstream pull/<this PR number>/head
    git merge --ff-only FETCH_HEAD
    git push
    ```
    

NOTE: As work continues on the original Pull Request, this process will
re-run and update (force-push) this Pull Request with updated style fixes as
necessary. If the style is fixed manually at any point (i.e. this process finds
no fixes to make), this Pull Request will be closed automatically.

Sorry if this was unexpected. To disable it, see our documentation.

tehampson and others added 12 commits June 30, 2022 14:42
…e size

Some implmentation of PersistentStorageDelegate use KeyValueStoreManager
which is not capable of giving the size of for the time being, which
makes this obligation impossible to fulfill right now.

After performing a code audit no one is currently using the
functionality to get the size, so this change is safe, but we need
platforms to adhear to the this updated description.

We also are now enforcing the PersistentStorageDelegate::SyncGetKeyValue
API such that we fill up the buffer up to the size provided even if the
buffer is not large enough. This is done so that in the case a version
downgrade needs to happen that (due to OTA revert, security reason, or
any other reason) we can make sure as long as TLV data was stored you
could still ensure that you are able to work in critical situations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants