fix(cache): switch to filesystem backend for CachedSession to resolve locking issues #12
Conversation
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
… locking issues Fix the "sqlite: bad parameter or other api misuse" error reported on Ubuntu, Windows, and Android by changing the requests_cache backend from sqlite to filesystem. This uses a directory-based cache instead of a single file, eliminating locking problems in concurrent environments. No breaking changes; cache behavior remains compatible. Fixes: FHPythonUtils#10, FHPythonUtils#11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose of This Pull Request
Overview of Changes
Fix the "sqlite: bad parameter or other api misuse" error reported on Ubuntu, Windows, and Android by changing the
requests_cachebackend from sqlite to filesystem.This uses a directory-based cache instead of a single file, eliminating locking problems in concurrent environments.
No breaking changes; cache behavior remains compatible.
Related Issue
Fixes #10, #11