Upgrade to hypersync-client 1.3.0 (streaming v2)#64
Conversation
- Bump hypersync-client 1.1.4 -> 1.3.0. - StreamConfig: drop response_bytes_floor/ceiling; make max_batch_size an optional no-cap (None => no block cap); add response_bytes_target (default 400000) and max_buffered_bytes (None => adaptive). Update the From impl and index.d.ts. - get_with_rate_limit: adapt to the new RateLimitResponse enum — response is now optional (null on HTTP 429); inspect rate_limit and retry.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (70)
✅ Files skipped from review due to trivial changes (38)
📝 WalkthroughWalkthroughThis PR upgrades the hypersync-client Node.js binding to version 1.3.0, introducing rate-limited response handling and improved stream configuration tuning. The update makes query responses nullable when rate-limited and replaces response-byte sizing controls with new target and buffering fields. ChangesHypersync-client 1.3.0 integration
Docs & site regeneration
🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
- package version 1.3.0 -> 1.4.0 (1.3.0 already on npm); synced the npm/* platform sub-packages via 'napi version'. - Regenerated index.d.ts / index.js from the 1.3.0 build (yarn build) and the typedoc HTML under docs/ (yarn docs) — StreamConfig now shows response_bytes_target / max_buffered_bytes and the optional rate-limited response. Built against published hypersync-client 1.3.0; release/publish runs in CI.
Upgrades the core dep
hypersync-client1.1.4 → 1.3.0 (streaming engine v2) and adapts the API.StreamConfig (breaking)
response_bytes_floor/response_bytes_ceiling.max_batch_sizeis now an optional no-cap (unset ⇒ no block cap; overshoot self-corrects via backfill).response_bytes_target(default 400000) — projection aims each response at this size.max_buffered_bytes(unset ⇒ adaptive reorder-buffer cap).From<StreamConfig>impl andindex.d.ts.Rate-limit API
getWithRateLimitadapts to the newRateLimitResponseenum:responseis now optional (nullon HTTP 429) — inspectrateLimitand retry.Verified with
cargo checkagainst publishedhypersync-client1.3.0. napi artifact build + publish happen in CI.Summary by CodeRabbit
Bug Fixes
New Features
Chores
Documentation