Соблюдение новых ограничений на длительность запросов

[leshchenko1979]

Fixes #187

[codecov]

Codecov Report

Attention: Patch coverage is 85.18519% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 84.05%. Comparing base (754de24) to head (5d398a8).

Files	Patch %	Lines
fast_bitrix24/srh.py	62.50%	6 Missing ⚠️
fast_bitrix24/leaky_bucket.py	96.77%	1 Missing ⚠️
fast_bitrix24/logger.py	83.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #217      +/-   ##
==========================================
- Coverage   89.32%   84.05%   -5.27%     
==========================================
  Files          10       11       +1     
  Lines         515      533      +18     
==========================================
- Hits          460      448      -12     
- Misses         55       85      +30     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sourcery-ai]

PR Type: Enhancement

PR Summary: This pull request introduces a new feature aimed at enforcing new request duration limits within the application. It includes the addition of a LeakyBucketLimiter class to manage request rates effectively, ensuring that the application adheres to specified constraints on the duration and frequency of requests. The changes span across multiple files, including the introduction of new tests to validate the functionality of the limiter and modifications to existing request handling logic to incorporate the new rate limiting strategy.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.

• Sourcery currently only approves 'Typo fix' PRs.

✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.

No details provided.

✅ Small diff: the diff is small enough to approve with confidence.

No details provided.

General suggestions:

• Given the significant changes introduced, especially with the addition of method-specific rate limiting, it's crucial to ensure comprehensive documentation is in place. This will help users and future maintainers understand the rationale behind these changes and how to work with the new rate limiting features.
• Consider simplifying the implementation if possible to reduce complexity. While the introduction of a LeakyBucketLimiter provides a robust solution for rate limiting, the added complexity could make the system harder to maintain and extend in the future.
• Ensure thorough testing of the new rate limiting logic under various scenarios, including high load and edge cases, to guarantee the system behaves as expected without introducing regressions.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

• X
• Mastodon
• LinkedIn
• Facebook

---

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.