chore(python): bump ruff to 0.15.12 and apply format

[mvanhorn]

Closes #2143.

Bumps ruff from 0.6.1 (mid 2024) to 0.15.12 (latest) and applies ruff format so the formatter check is in sync with the new version.

Changes

• python/aibrix/pyproject.toml: ruff = "0.6.1" -> ruff = "0.15.12".
• python/aibrix/poetry.lock: regenerated to lock ruff at 0.15.12. Generated with poetry 1.8.5 (lockfile header). The non-ruff diff is two reordered marker lists (uvloop, pandas numpy) — the resolved versions are identical.
• 13 files reformatted by ruff format. Each file is the exact set listed in the issue body. Diffs are formatter-only — ast.parse confirms identical ASTs before and after.

Verification

From python/aibrix/:

python -m ruff check .         # All checks passed!
python -m ruff format --check . # 169 files already formatted

Both gates from .github/workflows/python-aibrix-tests.yml pass cleanly with the new pin.

[gemini-code-assist]

Code Review

This pull request updates the ruff linter to version 0.15.12 and includes widespread reformatting of assert statements across the codebase, likely triggered by the linter update. Feedback focuses on the use of assert for runtime validation in production logic; it is recommended to replace these with explicit exceptions like RuntimeError or ValueError to prevent them from being optimized away in production environments.

[gemini-code-assist]

Using assert for runtime state validation in production code is discouraged because assertions can be disabled globally in Python (using the -O flag). If self.driver is None, it is better to raise an explicit exception like RuntimeError to ensure the check is always performed and provides a clear error message.

        if self.driver is None:
            raise RuntimeError("Driver must be initialized before executing jobs")

[gemini-code-assist]

Using assert for runtime state validation in production code is discouraged because assertions can be disabled globally in Python (using the -O flag). If self.driver is None, it is better to raise an explicit exception like RuntimeError to ensure the check is always performed and provides a clear error message.

        if self.driver is None:
            raise RuntimeError("Driver must be initialized before waiting for jobs")

[gemini-code-assist]

Using assert for runtime state validation in production code is discouraged because assertions can be disabled globally in Python (using the -O flag). If self.health_checker is None, it is better to raise an explicit exception like RuntimeError to ensure the check is always performed and provides a clear error message.

            if self.health_checker is None:
                raise RuntimeError("Health checker should be initialized")

[gemini-code-assist]

Using assert for state validation in production logic is risky because it can be optimized away. Consider raising a ValueError or a custom exception instead to ensure the check is always executed.

        if job_status.in_progress_at is None:
            raise ValueError("Job must be set as in progress before setting as ready")

[gemini-code-assist]

Using assert for validating input parameters or state in production code is not recommended. If the condition fails, it is better to raise a ValueError with a descriptive message to ensure the error is caught even in optimized environments.

Suggested change

	assert metric.name == self.original_name, (
	f"Metric name {metric.name} does not match Rule original name {self.original_name}"
	)
	if metric.name != self.original_name:
	raise ValueError(
	f"Metric name {metric.name} does not match Rule original name {self.original_name}"
	)

[gemini-code-assist]

Using assert for validating input parameters or state in production code is not recommended. If the condition fails, it is better to raise a ValueError with a descriptive message to ensure the error is caught even in optimized environments.

Suggested change

	assert metric.name == self.metric_name, (
	f"Metric name {metric.name} does not match Rule metric name {self.metric_name}"
	)
	if metric.name != self.metric_name:
	raise ValueError(
	f"Metric name {metric.name} does not match Rule metric name {self.metric_name}"
	)

[varungup90]

can you sign the PR.

[Jeffwan]

overall looks good to me. we make lots of changes to poetry recently, please rebase the master to fetch the latest code

[Jeffwan]

@mvanhorn could you help regenerate the lock file using higher poetry version

 This file is automatically @generated by Poetry 2.1.2 and should not be changed by hand