fix(api): Fix panics in API server if storage values cache is disabled #1370
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.
What ❔
Don't panic in
PostgresStorageCaches::schedule_values_update()
if the values cache was not configured.Why ❔
This leads to panics if the cache is disabled via config. Ignoring the update looks like more reasonable behavior.
Checklist
zk fmt
andzk lint
.zk spellcheck
.zk linkcheck
.