Skip to content

style: ruff-format tests/test_cli_hub_env.py (CI gate fix)#751

Merged
xdotli merged 1 commit into
release/v0.6.0from
fix/format-hub-env-test
Jun 13, 2026
Merged

style: ruff-format tests/test_cli_hub_env.py (CI gate fix)#751
xdotli merged 1 commit into
release/v0.6.0from
fix/format-hub-env-test

Conversation

@xdotli

@xdotli xdotli commented Jun 13, 2026

Copy link
Copy Markdown
Member

Follow-up to #750: that test rewrite passed ruff check but I hadn't run ruff format --check, which the CI test job runs as a gating step — it failed on Would reformat: tests/test_cli_hub_env.py. This applies ruff format (collapses the set comprehension to canonical form), no logic change. With this, #665's gate should go fully green (the ANSI test fix from #750 + this format fix were the only two failures). Verified locally: ruff format --check + ruff check + ty + the test all pass.


Note

Low Risk
Test-only whitespace/formatting; no production or assertion changes.

Overview
CI-only formatting fix for tests/test_cli_hub_env.py: ruff format collapses the visible set comprehension in test_environment_group_is_hidden_but_still_resolves to a single line. No test logic or assertions change—this unblocks the ruff format --check gate that failed after the prior test rewrite (#750).

Reviewed by Cursor Bugbot for commit 6842565. Bugbot is set up for automated code reviews on this repo. Configure here.

#750's test rewrite passed `ruff check` (lint) but I didn't run
`ruff format --check` — the CI `test` job runs format-check as a gating step and
failed on `Would reformat: tests/test_cli_hub_env.py`. This applies ruff format
(collapses the set comprehension to ruff's canonical form). No logic change.

Verified: ruff format --check + ruff check + ty + the test file all pass.
@xdotli xdotli merged commit 3ef837d into release/v0.6.0 Jun 13, 2026
1 of 2 checks passed
@xdotli xdotli deleted the fix/format-hub-env-test branch June 13, 2026 23:24
@cursor

cursor Bot commented Jun 13, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3521e66f-ae2d-4937-88cd-38e1e33f93c8)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant