There was an issue where two deb-s3 processes could write a lock file and continue to upload losing one the packages they were kicked off in the same time frame. This was relatively common when running concurrent CI builds.
To solve this I added a read check once a package is written so that it checks if it successfully holds the lock, using a random string to avoid instances where this happens on the same host.
There was an issue where two deb-s3 processes could write a lock file and continue to upload losing one the packages they were kicked off in the same time frame. This was relatively common when running concurrent CI builds.
To solve this I added a read check once a package is written so that it checks if it successfully holds the lock, using a random string to avoid instances where this happens on the same host.