Andrew Gaul
Andrew Gaul
Also shellcheck.
Could you test with the latest version 1.95?
What do the s3fs logs say? Launch s3fs with `-f -d`. Can you quantify how large is large? Do you have the same problem with AWS CLI, e.g., does idrive.com...
Please provide the logs that https://github.com/s3fs-fuse/s3fs-fuse/issues/2644#issuecomment-2670529006 suggested.
Sorry I missed the pastebin link. But this is truncated before the error occurs: ``` 2025-02-21T19:27:27.466Z [INF] curl.cpp:insertV4Headers(2892): computing signature [PUT] [/BigFile] [partNumber=295&uploadId=32767.7cad4117-8ede-4e72-b388-187eb1f6a462] [716a7dfa6c0453b9a0d6926fca212831c57616a2361eab38676fff06105e489b] 2025-02-21T19:27:27.467Z [INF] curl_util.cpp:url_to_host(334): url is https://w9v5.va21.idrivee2-1.com...
The S3 protocol is sometimes incompletely implemented. So idrive.com may have some issues that prevent use with AWS CLI (and maybe s3fs too). You might want to share this issue...
This is probably related to the Amazon client changes discussed here: https://news.ycombinator.com/item?id=43118592 tl;dr: just test with s3fs and share the complete logs as I requested.
@timuralp could you look into this?
It looks like `AliasBlobStore` should override `listMultipartUpload`. You should try modifying `AliasBlobStoreTest.testAliasMultipartUpload` to reproduce the symptom to confirm the problem before including the suggested fix.
JDK 20 deprecates many `URL` constructors so maybe this is not needed: https://javaalmanac.io/jdk/20/apidiff/19/