Skip to content

fix(adaptive): loosen rusqlite to ^0.40 - #57

Merged
sanil-23 merged 1 commit into
tinyhumansai:mainfrom
sanil-23:fix/adaptive-rusqlite-req
Aug 17, 2026
Merged

fix(adaptive): loosen rusqlite to ^0.40#57
sanil-23 merged 1 commit into
tinyhumansai:mainfrom
sanil-23:fix/adaptive-rusqlite-req

Conversation

@sanil-23

Copy link
Copy Markdown
Contributor

A host workspace that also links a crate pinning rusqlite = "=0.40.0" (medulla's vendored OpenHuman core does) cannot resolve ^0.40.2 beside it — cargo unifies one semver-compatible range and the two requirements conflict. Nothing in the adaptive crate needs the point release, so the requirement is now "0.40".

Found wiring tinyflows-adaptive into medulla as a vendored path dependency.

🤖 Generated with Claude Code

A host workspace that also links a crate pinning rusqlite =0.40.0 (the
vendored OpenHuman core does) cannot resolve ^0.40.2 beside it — one
semver range, two incompatible requirements. Nothing here needs the
point release.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@sanil-23, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0003d2b7-3c5b-4bbe-8267-3f8385b8b4f8

📥 Commits

Reviewing files that changed from the base of the PR and between b964cac and 0b0e976.

📒 Files selected for processing (1)
  • crates/adaptive/Cargo.toml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@tinysweeper tinysweeper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tinysweeper found nothing blocking. Approving.

$0.0000 · 0 in / 0 out · 44 embedded · openrouter/openai/text-embedding-3-small

@tinysweeper tinysweeper Bot added the priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect. label Aug 17, 2026
@sanil-23
sanil-23 merged commit 83fd387 into tinyhumansai:main Aug 17, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant