Skip to content

feat(http): add circuit breaker and response size limit to HTTP client - #30

Merged
Praying merged 2 commits into
mainfrom
feat-reqwest-0.13
Jan 5, 2026
Merged

Praying merged 2 commits into
mainfrom
feat-reqwest-0.13

Conversation

@Praying

@Praying Praying commented Jan 5, 2026

Copy link
Copy Markdown
Owner
  • Integrate circuit breaker functionality with configurable parameters
  • Implement response size limit enforcement with streaming validation
  • Add configuration validation for HTTP client parameters
  • Include rate limiter configuration validation and precision improvements
  • Add ConfigValidationError type for configuration validation errors
  • Enhance WebSocket client with subscription state tracking methods
  • Add Binance exchange WebSocket connection state access methods
  • Update dependencies with regex and lazy_static workspace support
  • Add reqwest stream feature for response streaming capability

- Integrate circuit breaker functionality with configurable parameters
- Implement response size limit enforcement with streaming validation
- Add configuration validation for HTTP client parameters
- Include rate limiter configuration validation and precision improvements
- Add ConfigValidationError type for configuration validation errors
- Enhance WebSocket client with subscription state tracking methods
- Add Binance exchange WebSocket connection state access methods
- Update dependencies with regex and lazy_static workspace support
- Add reqwest stream feature for response streaming capability
- Removed lazy_static dependency from ccxt-core and root Cargo.toml
- Replaced lazy_static! macro with std::sync::LazyLock for SERVER_ERROR_PATTERN
- Updated circuit breaker timeout calculation to use u128::from(u64::MAX)
- Modernized string formatting with const formatting in error messages
- Cleaned up code by removing deprecated lazy_static usage
@Praying
Praying merged commit b6e30c9 into main Jan 5, 2026
9 checks passed
@Praying
Praying deleted the feat-reqwest-0.13 branch January 5, 2026 16:05
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