Caper

Latest version: v2.3.2

Safety actively analyzes 688313 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 15

1.6.2

1.6.1

- Raises exception `WomtoolValidationFailedException` when Womtool validation fails (instead of returning `False`)
- Fixed typo in warning message related `aws` backend's call-caching
- Installs `gsutil` on aws caper server instance

1.6.0

- AWS backend is updated and fully tested.
- Call-caching (re-using previous outputs) works fine but Cromwell always makes cache copies on new workflow's output directory even with `--aws-call-caching-dup-strat reference`. See [this issue](https://github.com/broadinstitute/cromwell/issues/6327) for details.

- Users can use HOCON's `include` statements in custom backend configuration file (specified with `--backend-conf`).

1.5.1

Fix `--backend-conf`
- `--backend-conf` will correctly override the auto-generated backend configuration file.
- Added a new parameter `update=False` to `HOCONString.merge()`, which will update `self` with merged if `update==True`.

1.5.0

If you upgrade from previous version then please upgrade `autouri` too.
bash
$ pip install autouri --upgrade
$ pip install caper --upgrade


Upgraded Cromwell from 52 to 59. Metadata DB is compatible between two versions.

Please check your Caper configuration file at `~/.caper/default.conf` to remove `cromwell` and `womtool` from the file. Then Caper will automatically download Cromwell/Womtool 59 and use them.
ini
remove these two lines
cromwell=~/.caper/cromwell_jar/cromwell-52.jar
womtool=~/.caper/womtool_jar/womtool-52.jar


Fixed a bug that takes too long to recursively localize big files from S3 to GCS
- md5 checksum skipping flag was not propagated for recursive localization (in JSON, CSV, TSV) in `autouri`
- Fixed in `autouri`

If you get the following error, then check your service account's settings [this document](https://github.com/ENCODE-DCC/caper/blob/master/docs/conf_gcp.md#how-to-run-caper-with-a-service-account).

400 Bad Request
POST https://lifesciences.googleapis.com/v2beta/projects/XXX/locations/us-central1/operations/XXX:cancel
{
"code" : 400,
"errors" : [ {
"domain" : "global",
"message" : "Precondition check failed.",
"reason" : "failedPrecondition"
} ],
"message" : "Precondition check failed.",
"status" : "FAILED_PRECONDITION"
}

1.4.2

Parameter name changes
- `auto-update-metadata` -> `auto-write-metadata`: in both CLI and python functions (`_` instead of `-`).

Generation of `metadata.json` file on workflow's root output directory
- It was written for any change in task/subworkflow/workflows status change, which possibly stressed Cromwell server and resulted in its crash. It's written only when a main workflow is done whether successful or not.

Bug fixes
- Fix wrong graceful shutdown message even when Cromwell is done successfully.

Page 3 of 15

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.