Skip to content

Fix: Ensure consistent error handling in coordinate_compression.py #16233

Fix: Ensure consistent error handling in coordinate_compression.py

Fix: Ensure consistent error handling in coordinate_compression.py #16233

Triggered via pull request October 31, 2025 17:25
Status Failure
Total duration 15s
Artifacts

ruff.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors
ruff
Process completed with exit code 1.
Ruff (E501): data_compression/coordinate_compression.py#L100
data_compression/coordinate_compression.py:100:89: E501 Line too long (102 > 88)
Ruff (EM102): data_compression/coordinate_compression.py#L100
data_compression/coordinate_compression.py:100:30: EM102 Exception must not use an f-string literal, assign to variable first
Ruff (EM102): data_compression/coordinate_compression.py#L76
data_compression/coordinate_compression.py:76:26: EM102 Exception must not use an f-string literal, assign to variable first
Ruff (UP006): data_compression/coordinate_compression.py#L35
data_compression/coordinate_compression.py:35:32: UP006 Use `list` instead of `List` for type annotation
Ruff (UP035): data_compression/coordinate_compression.py#L24
data_compression/coordinate_compression.py:24:1: UP035 `typing.List` is deprecated, use `list` instead
Ruff (RUF002): data_compression/coordinate_compression.py#L5
data_compression/coordinate_compression.py:5:47: RUF002 Docstring contains ambiguous `’` (RIGHT SINGLE QUOTATION MARK). Did you mean ``` (GRAVE ACCENT)?