Flowise
Flowise copied to clipboard
feat: handle 429 errors and redirect to rate-limited page
- Adds a rate-limited page
- Handle 429 TOO MANY REQUESTS errors and redirect to rate-limited page
Summary of Changes
Hello @0xi4o, I'm Gemini Code Assist[^1]! 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 enhances the application's robustness and user experience by gracefully handling API rate-limiting scenarios. It introduces a new user interface to inform users about rate limits and provides a mechanism to automatically redirect them to this page when a 429 error occurs, along with a countdown before they can retry their actions.
Highlights
- New Rate-Limited Page: Introduced a dedicated
RateLimitedPagecomponent to inform users when they have exceeded API rate limits, providing a clear message and a countdown timer. - 429 Error Handling: Implemented global error handling within
ErrorContextto detect HTTP 429 (Too Many Requests) errors and automatically redirect users to the new rate-limited page. Theretry-afterheader is used to set the initial countdown. - User Experience: The new page includes a 'Try Again' button that becomes active after the countdown, and a 'Back to Home' button for authenticated users, improving the user experience during rate-limiting events.
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 :thumbsup: and :thumbsdown: 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.
[^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.
What will happen when LLM provider returns a 429 error? Will user be redirected to this 429 page or The error message (e.g., “429: Rate limit exceeded”) will appear directly in the chat box?
When LLM providers return a 429 error, we catch it and return a 500 to the frontend. So those won't redirect to the rate-limited page.