Skip to content

chore(main): Fix lint failures in lib/fixtures on main#3084

Merged
elizabethhealy merged 1 commit intomainfrom
fix-lint-lib-fixtures
Feb 18, 2026
Merged

chore(main): Fix lint failures in lib/fixtures on main#3084
elizabethhealy merged 1 commit intomainfrom
fix-lint-lib-fixtures

Conversation

@elizabethhealy
Copy link
Member

@elizabethhealy elizabethhealy commented Feb 18, 2026

Proposed Changes

  • This pull request addresses linting failures in the lib/fixtures directory by performing targeted refactorings in keycloak.go

Checklist

  • I have added or updated unit tests
  • I have added or updated integration tests (if appropriate)
  • I have added or updated documentation

Testing Instructions

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @elizabethhealy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses linting failures in the lib/fixtures directory by performing targeted refactorings in keycloak.go. The changes streamline Keycloak utility functions through the removal of a redundant helper and a clearer implementation of error handling during user creation, enhancing overall code quality and maintainability.

Highlights

  • Code Cleanup: Removed the redundant createRealm helper function, which was a wrapper around createRealmWithTokenManager.
  • Error Handling Refinement: Refactored the error handling logic within the createUser function to improve clarity and structure, particularly for http.StatusConflict cases.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • lib/fixtures/keycloak.go
    • Removed the createRealm function.
    • Refactored the error handling logic in createUser to better manage http.StatusConflict and other error scenarios.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Code linting runs, Errors found, then swiftly fixed, Clean code now shines bright.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily refactors and improves the lib/fixtures/keycloak.go file, specifically streamlining the createRealm function and enhancing error handling in createUser for better readability and maintainability. However, a medium-severity log injection vulnerability has been identified where an unsanitized username is used in error messages, potentially allowing for log spoofing. A recommendation to mitigate this issue has been provided.

@github-actions
Copy link
Contributor

Benchmark results, click to expand

Benchmark authorization.GetDecisions Results:

Metric Value
Approved Decision Requests 1000
Denied Decision Requests 0
Total Time 190.929686ms

Benchmark authorization.v2.GetMultiResourceDecision Results:

Metric Value
Approved Decision Requests 1000
Denied Decision Requests 0
Total Time 89.778724ms

Benchmark Statistics

Name № Requests Avg Duration Min Duration Max Duration

Bulk Benchmark Results

Metric Value
Total Decrypts 100
Successful Decrypts 100
Failed Decrypts 0
Total Time 377.30526ms
Throughput 265.04 requests/second

TDF3 Benchmark Results:

Metric Value
Total Requests 5000
Successful Requests 5000
Failed Requests 0
Concurrent Requests 50
Total Time 38.754919045s
Average Latency 385.047748ms
Throughput 129.02 requests/second

@elizabethhealy elizabethhealy marked this pull request as ready for review February 18, 2026 16:13
@elizabethhealy elizabethhealy requested review from a team as code owners February 18, 2026 16:13
@elizabethhealy elizabethhealy added this pull request to the merge queue Feb 18, 2026
Merged via the queue into main with commit e477375 Feb 18, 2026
43 checks passed
@elizabethhealy elizabethhealy deleted the fix-lint-lib-fixtures branch February 18, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments