[BUG] Incorrect rate_limit string due to static class attribute

[Ankitpardeshiii]

Bug Description

The rate_limit field in the Settings config is evaluated at class definition time instead of runtime. Because it depends on rate_limit_max_requests and rate_limit_window, changes from environment variables are not reflected, resulting in incorrect rate limit values.

To Reproduce

1. Set in .env:
   RATE_LIMIT_MAX_REQUESTS=10
   RATE_LIMIT_WINDOW=120
2. Start the backend.
3. Log or print settings.rate_limit.

Expected Behavior

rate_limit should dynamically reflect the current values.
Example: 10 requests per 120s

Actual Behavior

The value remains 30 requests per 60s (default) even after env changes.

Screenshots/Logs

INFO: Loaded rate limit: 30 requests per 60s
Expected: 10 requests per 120s

Environment

OS: Windows 11
Shell: PowerShell 5.1
Node.js: 18.17.0
Python: 3.11.x
Coderrr: 1.1.0

Additional Context

This happens because rate_limit is a static class attribute instead of a computed property.

Checklist

• I have searched for similar issues
• I have included all requested information
• I have verified .env
• I have tested the latest version

[github-actions]

📌 Thanks for reporting an issue!

Please ensure you have:

• Searched for existing issues to avoid duplicates.
• Included steps to reproduce (if reporting a bug).
• Described the expected vs actual behavior.
• Provided any relevant logs or screenshots.

We will look into this as soon as possible.

[Akash-nath29]

Assigned to you @Ankitpardeshiii