Skip to content

style: fix black formatting on test_import_footprint.py#15

Merged
hampsterx merged 1 commit into
masterfrom
chore/black-format-import-footprint-test
Jul 1, 2026
Merged

style: fix black formatting on test_import_footprint.py#15
hampsterx merged 1 commit into
masterfrom
chore/black-format-import-footprint-test

Conversation

@hampsterx

Copy link
Copy Markdown
Owner

Summary

  • Fixes the failing Lint and type-check CI job on master: black --check flagged tests/test_import_footprint.py as unformatted (a multi-line .format() call that black collapses to one line)
  • The file was committed unformatted in earlier import-footprint work; this is a pure formatting fix, no behavior change

Changes

 tests/test_import_footprint.py | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

Test plan

  • black --check snowflake_sql_api tests passes locally (black 26.1.0, within the pinned >=24.0,<26.6)
  • CI Lint and type-check job green

Collapse a multi-line .format() call onto one line so `black --check` passes.
The file was committed unformatted, failing the Lint and type-check CI job on
master (unrelated to any feature change).
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@hampsterx, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7e5955f0-2dff-41d7-8266-218feea82b39

📥 Commits

Reviewing files that changed from the base of the PR and between 73cd4f6 and e7bc3dc.

📒 Files selected for processing (1)
  • tests/test_import_footprint.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/black-format-import-footprint-test

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hampsterx hampsterx merged commit d5862c8 into master Jul 1, 2026
7 checks passed
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