Octue

Latest version: v0.60.2

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

Scan your dependencies

Page 31 of 39

0.3.11

Not secure
Summary
Allow simpler instantiation of datasets from the cloud.

<!--- START AUTOGENERATED NOTES --->
Contents

Enhancements
- [x] Allow instantiation of datasets from any cloud directory rather than just those that have a dataset serialised as a `dataset.json` file in them

<!--- END AUTOGENERATED NOTES --->

0.3.10

Not secure
Summary
Improve the `Datafile` interface and allow instantiation with local and cloud paths simultaneously.

<!--- SKIP AUTOGENERATED NOTES --->
Contents

Enhancements
- [x] Allow `Datafile` instantiation with local and cloud paths simultaneously
- [x] Add `cloud_path` property to Datafile

Fixes
- [x] Ensure `Datafile` serializes with its `cloud_path` and `project_name`

Refactoring
- [x] Convert `Datafile.cloud_protocol`, `Datafile.bucket_name`, and `Datafile.path_in_bucket` to properties
- [x] Remove redundant `Datafile.reset_local_path` method
- [x] Simplify cloud location setting and getting within `Datafile`

<!--- END AUTOGENERATED NOTES --->

0.3.9

Not secure
Summary
Improve and simplify the `Datafile` interface and allow datafiles to simultaneously exist in the cloud and locally.

Contents

Enhancements
- [x] Allow datafiles to have a local and a cloud location simultaneously
- [x] If a local path is added to a cloud datafile, sync datafile changes to the new local file and the cloud object
- [x] Raise error if project name missing when attempting to instantiate a datafile from a cloud object
- [x] Make `Datafile` cloud location attributes public (`cloud_path`, `bucket_name`, `project_name`, `path_in_bucket`, `cloud_protocol`)
- [x] Add `Datafile.exists_locally` property

Fixes
- [x] Stop correct input and configuration manifest paths being overruled in `Runner.run`

Refactoring
- [x] Remove parameters from `Datafile` cloud methods except `Datafile.to_cloud` so that there is only one way to update the cloud location explicitly and none implicitly (this ties a single `Datafile` instance more strongly to a single cloud location)
- [x] Convert `Datafile.get_local_path` method to `Datafile.local_path` property
- [x] Rename `Datafile.is_in_cloud` to `Datafile.exists_in_cloud`

Testing
- [x] Fix incorrect dataset and datafile paths in manifest template app test

<!--- SKIP AUTOGENERATED NOTES --->

0.3.8

Not secure
Summary
Allow explicit non-lazy downloads of `Datafile`s and single-command downloads of all `Datafile`s in a `Dataset`.

<!--- SKIP AUTOGENERATED NOTES --->
Contents

Enhancements
- [x] Allow all files in a dataset to be downloaded at once

Fixes
- [x] Create non-existent intermediate directories when downloading files using `GoogleCloudStorageClient`

Refactoring
- [x] Move download logic from `Datafile.get_local_path` into new `download` method to allow explicit non-lazy downloads

Testing
- [x] Skip entire `octue.utils.processes` test class if on Windows
- [x] Improve use of mocks in processes test
- [x] Use made-up project name for most cloud tests

Operations
- [x] Use latest `conventional-commits` pre-commit hook
<!--- END AUTOGENERATED NOTES --->


Quality Checklist
- [x] New features are fully tested (No matter how much Coverage Karma you have)

0.3.7

Not secure
Summary
Add a function that makes it easy to run and capture any `stdout` and `stderr` output of subprocesses. This is useful for child services that forward their logs back to the parent as all output produced by non-python processes can be included.

<!--- START AUTOGENERATED NOTES --->
Contents

Enhancements
- [x] Add function for logging subprocess stdout and stderr

<!--- END AUTOGENERATED NOTES --->

Quality Checklist
- [x] New features are fully tested (No matter how much Coverage Karma you have)

0.3.6

Not secure
Summary
Allow services/children to be asked more than one question by a parent.

<!--- START AUTOGENERATED NOTES --->
Contents

Fixes
- [x] Use a new subscriber for each question/answer in `Service` so gRPC connections can be closed immediately after use but `Service` and `Child` instances can be reused
- [x] Ensure `Service` IDs always start with `octue.services` to avoid mismatches between topic/subscription names and `Service` IDs that resulted in broken communication between services
- [x] Make `input_values` parameter of `Child.ask` optional

Testing
- [x] Make `MockSubscriber` raise an error if used after being closed

<!--- SKIP AUTOGENERATED NOTES --->

Page 31 of 39

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.