Lapdog

Latest version: v0.18.10

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

Scan your dependencies

Page 3 of 12

0.17.3

Not secure
Bug Fixes:
* Added support for Dockstore methods
* Fixed sometimes breaking proxy service accounts during workspace creation

Other Changes:
* Cromwell logs should now always be uploaded, even if the submission crashes
* Added a spinner while launching submissions
* Submission errors now include `error-details` key in submission.json

0.17.2

Not secure
Bug Fixes:
* Fixed a bug with certain expressions not evaluating correctly

0.17.1

Not secure
**Deprecation Warning:** `lapdog.gateway.get_access_token()` is now deprecated and will be removed when Lapdog shifts to full release.
If you need to authenticate as the current user, use `lapdog.gateway.get_user_session()`, which returns a prebuilt
`AuthorizedSession` object which can be used to make authenticated requests on behalf of the user. This function only attaches the
OAuth scopes needed by Lapdog, so if you need additional scopes,
use `lapdog.cloud.utils.generate_default_session()`, which allows
requesting arbitrary scopes

**Deprecation Warning:** Changing the _query\_limit_ parameter to `lapdog.WorkspaceManager.execute()`
is no longer supported and will be removed when Lapdog shifts to full release.

New Features:
* Added a workaround for Authorized Domain workspaces

Other Changes:
* Restricted usage scopes of access tokens
* Standardized functions for getting current gcloud accounts
* From now on, newly deployed Lapdog functions will not support unauthenticated access.
This will not change lapdog's api, however individuals calling Lapdog engine functions
outside the client will need to pass an `Authorization` header, or use `lapdog.gateway.get_user_session`,
which returns a `requests.session` object with your authorization token autofilled

0.17.0

Not secure
Bug Fixes:
* Fixed a bug which sometimes prevented functions from being deployed during a patch
* Fixed a bug in the preflight system which sometimes displayed outdated preflight results
* Fixed a missing success notification when uploading new method configurations

New Features:
* Lapdog now supports an optional per-workspace call-cache

Other Changes:
* Updated Dalmatian to 0.0.11
* Updated UI Dependencies

Additional Cromwell Changes

These additional changes have also been backported to the global Cromwell images used
by Lapdog versions 0.15.0-0.16.4.

* Significantly improved latency of Cromwell log
* Updated to Cromwell 41. This allows worker VMs to be labeled by their parent submission id

Patch Contents:
* Updated `submit` endpoint to v7 to accommodate call-cache

0.16.4

Not secure
Other Changes:
* Updated `resolve` internal endpoint to v4 (no patch necessary)
* This change raises requirements for inserting a namespace resolution
* Redacted previous versions
* Added additional checks at the start of engine initialization to check required
Firecloud permissions prior to making any changes

Patch Contents

This patch is non-critical and does not contain any endpoint updates.

* Added role definition for `Engine_Admin` role

0.16.3

Not secure
Bug Fixes:
* Fixed an offline workspace with a cold cache disabling ui (87)
* Fixed page navigation logging an error to the console during workspace sync

Other Changes:
* Updated required version of Google Cloud SDK to `241.0.0`
* During startup, lapdog will print any critical alerts to the terminal
* Lowered the offline threshold for `WorkspaceManager.execute` to 100 entities
* Significant speed improvements to `WorkspaceManager.execute` when preparing a
submission in offline mode
* Aborting a submission now generates a Hound log entry
* UI link previews timeout after 10s and display a fallback dialog
* Speed improvements to `WorkspaceManager.mop`, `WorkspaceManager.list_submissions`, and UI link previews

Page 3 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.