...
Issue | bb | db | nw | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Re the orphaned chunk issue (
So the scenario we are talking about is as follows:
We have a tool for identifying orphanned chunks and removing them which we have used successfully in the recent past. We could force the synctool to perform a cleanup when it detects matching files. Or we could support that feature when a flag is enabled. Or it would also be possible to prevent the cleanup, when a flag is present. As far as duracloud operations are concerned, making cleanup on matching files the default behavior and providing a flag to suppress it for power users is optimal since we won't have to worry about scrubbing spaces after users upgrade to 6.1.0. For the users, the best option is for us not to implement "cleanup on checksum match" behavior at all and scrub their repositories once they upgrade to the new synctool. | Thanks for calling this out Danny. I know that the scenario you're calling out has occurred, but it is definitely an edge case. Considering that we have other tooling to discover and clean up this issue directly I don't think it's necessary to burden the SyncTool process with checking for orphaned files on each file it touches. That has the potential to significantly slow down the sync process, especially if many small files are being transferred. I'll make the call to leave the SyncTool as-is for 6.1. We will definitely want to encourage all users to upgrade to the new SyncTool as soon as it is available. | ||||||||||
|
Testing of Completed Issues
...
Task | bb | db | nw |
---|---|---|---|
Perform Regression Tests | |||
Use ZAProxy to perform a security analysis
| duracloud-6.1.0-zaproxy-report.html |
Build Tests
Test | bb | db | nw |
---|---|---|---|
mvn clean install (full build + integration tests) - DuraCloud |
Integration tests fail frequently due to a "space already exists" error. See issue #2. | (Two tests failed, but upon further investigation it was clear that they were false positives) |
Release Actions - for each baseline (in this order): DB, DuraCloud, MC, Snapshot, Mill
...