I opened a pull request:
https://github.com/apache/jclouds/pull/94
On Fri, Jan 08, 2021 at 10:01:56AM +0900, Andrew Gaul wrote:
> Hi John, the code in LocalBlobStore.putBlob looks like this:
>
> String eTag = storageStrategy.putBlob(containerName, blob);
>
I looked over the code changes myself and I agree with you. It's unlikely
anything in jclouds is causing this error. I'm currently investigating issues
without build system where the tmp directory may be close to full or some other
space/perms-related issue.
Thanks,
John
I looked through:
git log upstream/2.2.x blobstore/
git log upstream/2.2.x apis/filesystem/
But there are only a few changes and I do not believe that these commits
could cause your symptoms. You could try bisecting to be sure. Given
that my suggested race condition is so easy to fix I
Hi Andrew,
Your theory about another client deleting the file cannot be correct. This is
an integration test where a single test is running - the container is created
in /tmp//test-container. The test creates the test
container in the setup method, uploads several files, manipulates some data,
Hi John, the code in LocalBlobStore.putBlob looks like this:
String eTag = storageStrategy.putBlob(containerName, blob);
setBlobAccess(containerName, blobKey, options.getBlobAccess());
I suspect that the object is being removed by another client in between
these calls. Instead
One more comment - it's an intermittent failure. Sometimes it works, sometimes
not.
We use the filesystem (LocalBlobStore) implementation for integration testing
in our code.
I'm seeing the following behavior in version 2.2.1 which I recently upgraded to:
```
2021-01-07 20:03:43.503,7964896021968234 {} DEBUG
c.p.d.m.j.AbstractUploadCallable [cpu-normalpri-1] [task 1] State
