Closed michaelchen01 closed 2 months ago
Hi @michaelchen01 is there any parameter DEFAULT_STORAGE_CLIENT_TIMEOUT
that you defined? While initializing the storage client?
@michaelchen01 updating storage3
manually helped me, because after updating supabase
, it conflicts with older storage3
. As I see:
def _init_storage_client( storage_url: str, headers: Dict[str, str], storage_client_timeout: int = DEFAULT_STORAGE_CLIENT_TIMEOUT, verify: bool = True, ) -> SyncStorageClient: return SyncStorageClient(storage_url, headers, storage_client_timeout, verify)
When older version of storage3 accept only 3 parameters:
def __init__( self, url: str, headers: dict[str, str], timeout: int = DEFAULT_TIMEOUT, ) -> None:
JFYI, New 'verify' parameter was added here on Jun 4, 2024
gotcha!
Yes this would be due to dependency not being updated. Update your dependencies and this should work.
Bug report
Describe the bug
Initializing the current storage client (either via a synchronous client or asynchronous client) results in this error
AsyncStorageClient.__init__() takes from 3 to 4 positional arguments but 5 were given
I am initializing it according to the docs, but lmk if that's not correct. The client itself is initialized as:
FWIW, I also tried with the synchronous client, and am seeing the same behavior. I've also tried deleting my virtual env + clean install and it still repros. Currently trying to figure out which version works.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
supabase.storage
at runtime.Expected behavior
The supabase storage client should be instantiated without throwing an error.
Screenshots
More of the stack trace:
System information
Additional context
Add any other context about the problem here.