Fix screenshot functionality and add API key based ratelimiting - #16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces rate limiting for API requests in the backend, improves image handling for OpenAI endpoints, and adds several new dependencies to support these features. The most significant changes are the addition of per-API-key rate limiting to prevent abuse and the enhancement of image input support. Below are the top changes grouped by theme:
Rate Limiting Implementation:
ratelimitmodule (backend/src/ratelimit.rs) that uses thegovernor,dashmap, andonce_cellcrates to enforce a limit of 3 requests per minute per API key. Thecheck_rate_limitfunction is now called in the OpenAI endpoint to reject requests exceeding the limit. [1] [2] [3] [4]Cargo.tomlto include new dependencies:dashmap,governor, andonce_cellfor thread-safe rate limiting.OpenAI Image Handling Improvements:
get_step_by_step_guidanceandget_final_answerfunctions to accept either raw base64 strings or full data URLs, making the API more robust to different input formats. [1] [2]Frontend Configuration: