|
2 | 2 | Release History |
3 | 3 | =============== |
4 | 4 |
|
| 5 | +v0.0.22 (2025-05-18) |
| 6 | +==================== |
| 7 | + |
| 8 | +Added |
| 9 | +----- |
| 10 | + |
| 11 | +- Support for ``bluesky.protocols.NamedMovable`` protocol. |
| 12 | + |
| 13 | +- Support for the new CLI parameters: ``--ipython-connection-dir``, ``--ipython-connection-file``, |
| 14 | + ``--ipython-shell-port``, ``--ipython-iopub-port``, ``--ipython-stdin-port``, ``--ipython-hb-port``, |
| 15 | + ``--ipython-control-port``. |
| 16 | + |
| 17 | +- Support for the new environment variables: ``QSERVER_IPYTHON_KERNEL_CONNECTION_FILE``, |
| 18 | + ``QSERVER_IPYTHON_KERNEL_CONNECTION_DIR``, ``QSERVER_IPYTHON_KERNEL_IOPUB_PORT``, |
| 19 | + ``QSERVER_IPYTHON_KERNEL_HB_PORT``, ``QSERVER_IPYTHON_KERNEL_CONTROL_PORT``, |
| 20 | + ``QSERVER_IPYTHON_KERNEL_SHELL_PORT``, ``QSERVER_IPYTHON_KERNEL_STDIN_PORT``. |
| 21 | + |
| 22 | +- Support for the new parameters in the ``worker`` section of RE Manager config file: |
| 23 | + ``ipython_connection_file``, ``ipython_connection_dir``, ``ipython_shell_port``, ``ipython_iopub_port``, |
| 24 | + ``ipython_stdin_port``, ``ipython_hb_port``, ``ipython_control_port``. |
| 25 | + |
| 26 | +- New parameter for setting 0MQ message encoding added to RE Manager and the clients: |
| 27 | + ``--zmq-encoding`` CLI parameter, ``QSERVER_ZMQ_ENCODING_FOR_SERVER`` environment variable and |
| 28 | + ``network/zmq_encoding`` config file parameter. |
| 29 | + |
| 30 | +Fixed |
| 31 | +----- |
| 32 | + |
| 33 | +- Fixed an issue with handling of ``collections.abc.Iterable`` plan parameter type. |
| 34 | + |
| 35 | +Changed |
| 36 | +------- |
| 37 | + |
| 38 | +- The built-in feature that allowed instantiation and configuring Run Engine was removed. |
| 39 | + Now Run Engine must be instantiated and configured in the startup code. |
| 40 | + |
| 41 | +- The following CLI parameters were removed: ``--kafka-topic``, ``--kafka-server``, |
| 42 | + ``--zmq-data-proxy-addr``, ``--use-persistent-metadata`` and ``--databroker-config``. |
| 43 | + |
| 44 | +- RE Manager accepts ``--keep-re`` CLI parameter. The value of the parameter is ignored. |
| 45 | + RE Manager always work as if the option is enabled. Deprecation message is printed. |
| 46 | + |
| 47 | +- The ``run-engine`` section is removed from the config file (``use_persistent_metadata``, |
| 48 | + ``kafka_server``, ``kafka_topic``, ``zmq_data_proxy_addr``, ``databroker_config``). The server |
| 49 | + accept ``startup/keep_re`` parameter. The parameter value is ignored, deprecation message is printed. |
| 50 | + |
| 51 | +- The following packages are removed from dependencies: ``bluesky-kafka``, ``databroker``, |
| 52 | + ``event_model``, ``msgpack``, ``msgpack_numpy``. |
| 53 | + |
| 54 | +- Now RE Manager can successfully load startup code, which does not create an instance of Run Engine |
| 55 | + (``environment_open`` operation would fail in the past). In this case, RE Manager returns status |
| 56 | + parameter ``re_state: None`` and attempts to start the queue or individual plan fail with appropriate |
| 57 | + error messages. Clients are still able to execute scripts or functions in the environment. Run Engine |
| 58 | + may be instantiated and configured (e.g. by uploading a script) before any plans are executed. |
| 59 | + |
| 60 | + |
5 | 61 | v0.0.21 (2024-09-29) |
6 | 62 | ==================== |
7 | 63 |
|
|
0 commit comments