-
Notifications
You must be signed in to change notification settings - Fork 293
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
fix: Do not persist storage when it is configured #559
base: master
Are you sure you want to change the base?
Conversation
@@ -57,7 +62,7 @@ def get_storage_client(*, client_type: StorageClientType | None = None) -> BaseS | |||
return _services['cloud_storage_client'] | |||
|
|||
if 'local_storage_client' not in _services: | |||
_services['local_storage_client'] = MemoryStorageClient() | |||
_services['local_storage_client'] = MemoryStorageClient(configuration=configuration) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if there is a local_storage_client
with a different configuration though? I'm afraid we'll need some changes on an architectural level...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we even store those two separately? those should be two flavors of a single service, not two different services, at least that's how it was designed in the js version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you mean why we have a separate local_storage_client
and cloud_storage_client
, we do this so that the force_cloud
switch in the SDK works. In the JS SDK, the Actor
class holds the cloud client. This feels more readable to me.
8cebe25
to
17595f3
Compare
17595f3
to
bf000e4
Compare
bf000e4
to
e49a7ae
Compare
Closes: #539