feat(native): offline caching#1585
Draft
jpnurmi wants to merge 2 commits intojpnurmi/feat/http-retryfrom
Draft
Conversation
The native daemon uses the same HTTP transport, so it gets offline caching for free as long as the cache_keep option is propagated via shared memory. Also, disable http_retry in the daemon since it is a single-shot process where retry backoff makes no sense. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Replace fixed 2s sleep with wait_for_file polling (up to 10s) for the cache_keep=True case. On slow CI machines the daemon may not finish writing the cache file within 2 seconds. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Note
Depends on HTTP retry because it moves caching from startup to the HTTP transport:
The native daemon uses the same HTTP transport, so it gets offline caching for free as long as the
cache_keepoption is propagated via shared memory. Also, disablehttp_retryin the daemon since it is a single-shot process where retry backoff makes no sense.See also: