Skip to content

fix(ci): apply rustfmt to cluster auth throttle helper - #187

Merged
AlexanderWagnerDev merged 2 commits into
security/cluster-auth-tracker-saturationfrom
fix/ci-rustfmt-cluster-auth
Sep 4, 2026
Merged

fix(ci): apply rustfmt to cluster auth throttle helper#187
AlexanderWagnerDev merged 2 commits into
security/cluster-auth-tracker-saturationfrom
fix/ci-rustfmt-cluster-auth

Conversation

@cursor

@cursor cursor Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Fixes CI failure on #186 where cargo fmt --check rejected formatting of all_cluster_auth_buckets_throttled in src/cluster/security.rs.

Applies cargo fmt to match the project's rustfmt rules.

Open in Web View Automation 

Note

Low Risk
Formatting-only Rust change with no logic or security behavior differences; lockfile is a minor dependency patch bump.

Overview
Fixes cargo fmt --check CI by reformatting all_cluster_auth_buckets_throttled in src/cluster/security.rs: the signature and the .values().all(...) closure are laid out per project rustfmt rules. Behavior is unchanged—still returns whether every tracked IP bucket is at the cluster auth failure limit.

Cargo.lock also bumps transitive tinyvec from 1.13.1 to 1.13.2 (checksum only; no source edits tied to it).

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

cursoragent and others added 2 commits September 4, 2026 05:01
Co-authored-by: Alexander Wagner <info@alexanderwagnerdev.com>
@AlexanderWagnerDev
AlexanderWagnerDev marked this pull request as ready for review September 4, 2026 22:05
@AlexanderWagnerDev
AlexanderWagnerDev merged commit 942e97a into security/cluster-auth-tracker-saturation Sep 4, 2026
5 checks passed
@AlexanderWagnerDev
AlexanderWagnerDev deleted the fix/ci-rustfmt-cluster-auth branch September 4, 2026 22:05
@cursor

cursor Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

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_ee8e7a7d-02f5-4437-abf5-c4102a3be198)

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.

2 participants