Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rate limit error reporting #694

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

arionrefat
Copy link
Contributor

  • Added rate limiting to Sentry transport to prevent overwhelming Sentry with too many events
  • Limited to 10 logs per second with 1000ms interval
  • Queues additional logs when rate limit is exceeded
  • Preserves all existing Sentry logging functionality including error capturing and message handling
  • Added reference to Node types for setImmediate support

- Added comprehensive cleanup of podman containers, pods, and images
- Implemented removal of podman configuration folders
- Improved error handling during uninstallation
- Restored electron app path import for home directory access
- Replace any types with proper TypeScript utility types
- Add ThisParameterType, Parameters, and ReturnType generics
- Create QueueItem type for better type safety in FIFO queue
Copy link

netlify bot commented Mar 18, 2025

Deploy Preview for nndesign ready!

Name Link
🔨 Latest commit 4b29a23
🔍 Latest deploy log https://app.netlify.com/sites/nndesign/deploys/67d9b702a22d2d0008915b4d
😎 Deploy Preview https://deploy-preview-694--nndesign.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@arionrefat arionrefat changed the title refactor: enhance type safety in rate limiter implementation Rate limit error reporting Mar 18, 2025
@arionrefat
Copy link
Contributor Author

arionrefat commented Mar 18, 2025

@jgresham This is what I implemented, can you please check if I doing it properly?

- Renamed rateLimitedLog to normalLogRateLimiter for clarity
- Updated logging logic to bypass rate limiting for errors and fatal logs
- Ensured normal messages are still subject to rate limiting
- Included a comment attributing the original source of the rate limiting code
- Added MIT License notice for clarity and compliance
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