Sdss-clu

Latest version: v2.2.7

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

Scan your dependencies

Page 4 of 8

1.9.2

✨ Improved

* The `click` context object can now be access as `Command.context` if the `click` parser is being used.

1.9.1

🔧 Fixed

* Deal with replies without value in `MockReplyList`.

1.9.0

🚀 New

* [111](https://github.com/sdss/clu/issues/111) If a `LegacyActor` uses the Click parser, and a connection to Tron is defined, adds a `tron-reconnect` command that can be used to force recreating the connection from the actor to Tron.

🔧 Fixed

* Avoid setting the event loop on init in `CallbackMixIn`. This caused the event loop to not be running in some cases when `notify()` was invoked.
* Reworked how `TronConnection` uses the reconnecting protocol so that it actually reconnects.

1.8.2

🔧 Fixed

* [110](https://github.com/sdss/clu/issues/110) If the content of a keyword in `LegacyActor` is empty, output the keyword without the equal sign (e.g., `test` instead of `test=`).

1.8.1

💥 Breaking changes

* Removed the `create_setup.py` file. Poetry should now support all its use-cases.

🚀 New

* Added a `KeywordStore` that stores each time a keyword was output. It can be enabled by passing ``store=True`` when instantiating an actor and accessed as ``actor.store``. See the documentation for more details.
* Added `cancel_command()`, `get_current_command_name()`, and `get_current_command_name()` to click parser.

1.7.0

💥 Breaking changes

* The client model for an actor is now updated if the actor outputs a property that is not in its schema. This is not necessarily a breaking change, but it modifies the expectation that the client will validate replies against the actor schema. With this change we indicate that validating and respecting its own schema is a task for the actor and not for the client. There are at least a couple cases for which having the client enforce the actor schema was problematic: if the actor has `patternProperties` those are legal properties but are not updated in the client model; and if the actor decides to output a non-validated message. With this change, if the client receives a property that is not in the actor schema, a new `Property` is created int eh actor `Model` and its value is updated. That `Property` has `Property.in_schema=False` to indicate that the property has not been validated. Note that this change does not affect the `TronConnection` models since those are defined by actorkeys.

🚀 New

* `Command.write()` can now be called with a `logging` level instead of a string message code. For example `Command.write(logging.DEBUG, text="Hi")` is equivalent to `Command.write("d", text="Hi")`.

🔧 Fixed

* Fixed a `ConnectionResetError` when closing the connection to a `TCPStreamServer`.

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.