Tiled

Fixed

- Compatibility with a change in Starlette v0.38.0

Added

- Add method to `TableAdapter` which accepts a Python dictionary.
- Added an `Arrow` adapter which supports reading/writing arrow tables via `RecordBatchFileReader`/`RecordBatchFileWriter`.

Changed

- Make `tiled.client` accept a Python dictionary when fed to `write_dataframe()`.
- The `generated_minimal` example no longer requires pandas and instead uses a Python dict.
- Remove unused pytest-warning ignores from `test_writing.py`.
- Rename argument in `hdf5_lookup` function from `path` to `dataset` to reflect change in `ophyd_async`

Added

- A `/healthz` endpoint, for use by orchestration infrastructure

Fixed

- A bug in `Context.__getstate__` caused picking to fail if applied twice.

Added
- Support partial download of an asset using the
[HTTP `Range` Header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Range).

Fixed
- When authenticated as a Service Principal, display the SP's uuid in
the client Context repr.
- The dependency `json-merge-patch`, introduced in v0.1.0b4, was missing from
some pip selectors.

Changed

- Minor implementation changes were necessary to make Tiled compatible with
Numpy 2.0.
- For improved security, the server-side array slicing function has been
refactored to avoid using `eval()`. To be clear: there were no known
exploitable vulnerabilities in the `eval()` approach. The input was validated
against a regular expression before being passed to `eval()`. However,
avoiding `eval()` altogether is better practice for defense-in-depth against
potential code injection attacks due to current or future bugs in Tiled or
its upstream dependencies.

Added

- Added a new HTTP endpoint, `PATCH /api/v1/metadata/{path}` supporting modifying
existing metadata using a `application/json-patch+json` or a
`application/merge-patch+json` patch.
- Added client-side methods for replacing, updating (similar to `dict.update()`),
and patching metadata.

Fixed

- Fixed regression introduced in the previous release (v0.1.0b1) where exceptions
raised in the server sent _no_ response instead of properly sending a 500
response. (This presents in the client as, "Server disconnected without
sending a response.") A test now protects against this class of regression.