The error originates from boto3. This seems to be a https://github.com/boto/boto3/issues/3113 with one possible solution being disabling threading. The problem does no occur on Python 3.8.10.
Does this happen on different python versions?
Hi, we ran into a bit of a problem storing artifacts in S3. In Python 3.10 when the files are large enough for multipart uploading to kick in, something goes wrong in boto3 with threading causing the upload to fail. (exact error being RuntimeError: cannot schedule new futures after interpreter shutdown
in https://github.com/allegroai/clearml/blob/master/clearml/storage/helper.py#L1452 ) Temporary workaround for this would be to disable threading by setting multipart
to false. This doesn't seem to work because for AWS S3 when the config is loaded in https://github.com/allegroai/clearml/blob/master/clearml/storage/helper.py#L334 and https://github.com/allegroai/clearml/blob/master/clearml/backend_config/bucket_config.py#L180 multipart
is set to true by default and not loaded from the config as far as I can tell. Is this intended behavior and I'm configuring stuff wrong or is this a bug?
The error originates from boto3. This seems to be a https://github.com/boto/boto3/issues/3113 with one possible solution being disabling threading. The problem does no occur on Python 3.8.10.
Does this happen on different python versions?