9c00648314
We shouldn't be throwing `RepositoryException` when the repository wasn't concurrently modified in an unexpected fashion (i.e. on the blob/file level). When we know that the known repo gen moved higher in terms of the generation tracked in master memory we should throw the concurrent snapshot exception. This change makes concurrent snapshot create and delete always throw the same exception, prevents unnecessary listings when the generation is known to be off and prevents future test failures in SLM tests that assume the concurrent snapshot exception is always thrown here. Without this change, the newly added test randomly fails the `instanceOf` assertion by running into a `RepositoryException`. |
||
|---|---|---|
| .. | ||
| licenses | ||
| src | ||
| build.gradle | ||