feat: cache responses from firmware update service and queue requests #5030
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.
To do so, we switched to
got
instead ofaxios
(hoping that they eventually upgradecacheable-request
, so we can cache POST requests using built-in methods). By queueing and caching requests we should be able to avoid a lot of unnecessary requests. Caching is controlled by the firmware update service, but the cache kept in memory, so it is evicted by restarts.