Lapdog

Latest version: v0.18.10

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

Scan your dependencies

Page 6 of 12

0.15.4

Not secure
New Features:
* `lapdog.WorkspaceManager`s will attempt to connect with a running lapdog UI (if present)
to initialize the operator cache with data from the UI's cache of this workspace
* Added autocomplete to config inputs when editing a method configuration in the UI

Bug Fixes:
* Fixed not being able to upload new method configurations if the version was inferred from "latest"
* Fixed being unable to submit jobs or check quotas if a regions file was not defined
* Fixed a bug in the patching process which prevented patches to projects without a regions file

Other Changes:
* `lapdog.WorkspaceManager.build_retry_set` now handles FireCloud submissions
* Synchronized methods of `lapdog.Operator` now have the proper docstrings
* Updated dependencies

Patch Contents
* Updated `quotas` endpoint to v3
* Updated `submit` endpoint to v5

0.15.3

Not secure
New Features:
* Added autocomplete for the `Entity` field in the UI when running a new job

Bug Fixes:
* `lapdog.gateway.quota_usage` now returns quota usage from all enabled compute regions, not just `us-central1`

Other Changes:
* `lapdog.prune_cache` now prints the size of data removed and kept, and returns the size of data removed

Patch Contents
* Updated `quotas` endpoint to v2 to support the above bugfix

0.15.2

Not secure
New Features:
* Added `lapdog.copyblob` and `lapdog.moveblob` to copy and move blobs

Bug Fixes:
* Fixed a bug in the CLI preventing new workspaces from being created using `lapdog workspace`
* Fixed a bug in offline expression evaluation which prevented some complex expressions from being parsed

Other Changes:
* Cleaned the error messages displayed in `lapdog doctor`
* `lapdog.Gateway` now has a better string representation

0.15.1

Not secure
New Features:
* Added `lapdog.provenance` to provide provenance of provided data

Bug Fixes:
* `lapdog.Gateway.compute_regions` now silently handles permission errors by returning the default compute region (`us-central1`)
* Fixed a bug which prevented users from re-selecting the default compute region in the UI after selecting another one
* Fixed a bug which allowed some protected files to be deleted by `lapdog.WorkspaceManager.mop()`

0.15.0

Not secure
New Features:
* Users can now choose a custom compute region when submitting jobs
* Administrators can change the list of allowed regions. [Read more](https://github.com/broadinstitute/lapdog/wiki/Instructions-for-Adminscompute-regions)
* Added dropdown menu to UI to select the compute region for a job

Other Changes:
* Removed the `zones` argument to `lapdog.WorkspaceManager.execute` in favor of `regions` argument to set compute region for job

Patch Contents
* Updated `submit` endpoint to v4 to support customizable compute regions
* Updated cromwell tag to `v0.15.0`

0.14.2

Not secure
New Features:
* Added `lapdog doctor` command to diagnose issues with lapdog

Other Changes:
* Resubmitting a job through the UI now retains the same network configuration as the original job
* Interrupting `lapdog.WorkspaceManager.mop()` with Ctrl+C will abort the process and return the results so far

Page 6 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.