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

Cache directory and database created even when cache_seed = None #679

Closed
afourney opened this issue Nov 14, 2023 · 2 comments
Closed

Cache directory and database created even when cache_seed = None #679

afourney opened this issue Nov 14, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@afourney
Copy link
Member

Prior to version 0.2.0, setting use_cache = False in the llm_config would prevent the .cache directory from being created.

The new method of disabling cache is to use seed = None (prior to 0.2.0b4) or cache_seed = None (after 0.2.0b4). However, setting the seed to None does not prevent the .cache folder from being created. In fact the following sqlite database gets initialized:

.cache/None/cache.db

This causes the fix in #593 to be less effective than with prior versions.

@joshkyh
Copy link
Collaborator

joshkyh commented Nov 17, 2023

I had a similar small discussion, that might be related, adding here for context if it helps..? #600 (comment)

@sonichi sonichi added the enhancement New feature or request label Nov 17, 2023
@afourney afourney closed this as completed Dec 6, 2023
@amanuel1782
Copy link

how to fix the issue of cache #when autogen is deployed in AWS lambda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants