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

Whatever you did to timezone / cache recently broke my AWS Lambda function #1107

Closed
ryanlampkin opened this issue Oct 23, 2022 · 3 comments
Closed

Comments

@ryanlampkin
Copy link

ryanlampkin commented Oct 23, 2022

I never had this problem before this week. Seems like you've made changes to utils [image below]. With respect to AWS lambda, I am not able to "make directory / store".

Untitled

@ryanlampkin
Copy link
Author

Last working version for me is 0.1.75

@ValueRaider
Copy link
Collaborator

Sorry about that. I've sent out a new release - 0.1.81

This was because I recently added a local caching store for timezone data, because accessing info[] first time is relatively expensive. It assumed access to default local cache folder.

I've also added function set_tz_cache_location(), in case there is somewhere you can write.

@ValueRaider
Copy link
Collaborator

This appears to be solved so will close.

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

No branches or pull requests

2 participants