update deps

[thedavidmeister]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to the latest revisions to align with upstream.
  • No changes to functionality, UI, or public APIs.
  • No user action required; behavior remains unchanged.

[coderabbitai]

Walkthrough

Updates submodule pointers for lib/rain.interpreter and lib/rain.orderbook.interface to newer commits. No source code or public API changes reported.

Changes

Cohort / File(s)	Summary
Submodule pointer updates lib/rain.interpreter, lib/rain.orderbook.interface	Advance submodule commits: rain.interpreter 08ba1364 → ff1d064d; rain.orderbook.interface 71612d2b → 698588ad. No code/public API changes in this repo.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ob int #2139 — Updates the same submodule pointers for lib/rain.interpreter and lib/rain.orderbook.interface.
• 2025 09 04 float #2128 — Also updates the same submodule references for these two libraries.

Suggested reviewers

• hardyjosh

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The PR title "update deps" does match the change type—this PR updates submodule pointers for lib/rain.interpreter and lib/rain.orderbook.interface with no public API changes—but it is overly generic and uses shorthand that does not identify which dependencies or the scope of the update, so it does not clearly communicate the primary change to reviewers. The repository guidance prefers concise but specific titles, so the current title is insufficiently descriptive. Therefore the check is inconclusive.	Rename the PR to explicitly name the updated dependencies (for example "bump rain.interpreter and rain.orderbook.interface submodules"), and optionally add "pointer-only bump, no API changes" or the relevant commit SHAs in the title or first line of the description to clarify scope; this will make the change immediately clear to reviewers and improve project history.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 2025-09-16-exponent-overflow

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 13bf0d7 and 266e7d3.

📒 Files selected for processing (2)

• lib/rain.interpreter (1 hunks)
• lib/rain.orderbook.interface (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-07-04T09:02:57.301Z

Learnt from: findolor
PR: rainlanguage/rain.orderbook#1956
File: crates/common/src/fuzz/mod.rs:64-64
Timestamp: 2025-07-04T09:02:57.301Z
Learning: In rainlanguage/rain.orderbook, user findolor prefers to limit type consistency changes to only the parts directly related to the current work scope. For example, when updating chain_id fields from u64 to u32 in fuzz-related code, unrelated files like tauri-app wallet commands can remain as u64 if they serve different purposes and aren't part of the current changes.

Applied to files:

• lib/rain.orderbook.interface

📚 Learning: 2025-07-16T10:40:05.717Z

Learnt from: findolor
PR: rainlanguage/rain.orderbook#2000
File: crates/common/src/raindex_client/vaults.rs:183-183
Timestamp: 2025-07-16T10:40:05.717Z
Learning: In the rainlanguage/rain.orderbook codebase, user findolor considers breaking changes from Option<U256> to U256 for required fields like decimals in RaindexVaultToken to be acceptable and safe, even when they affect multiple usage sites across the codebase.

Applied to files:

• lib/rain.orderbook.interface

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)

• GitHub Check: standard-tests (ubuntu-latest, rainix-sol-test)
• GitHub Check: standard-tests (ubuntu-latest, rainix-rs-artifacts, true)
• GitHub Check: standard-tests (ubuntu-latest, rainix-rs-static)
• GitHub Check: standard-tests (ubuntu-latest, ob-rs-test, true)
• GitHub Check: Deploy-Preview-Push
• GitHub Check: git-clean
• GitHub Check: build-tauri (ubuntu-22.04, true)
• GitHub Check: test
• GitHub Check: test
• GitHub Check: test

🔇 Additional comments (2)

lib/rain.orderbook.interface (1)

1-1: Submodule bump — add upstream change summary and confirm no breaking/security impact

• Ran the verification script:

  • lib/rain.orderbook.interface: 71612d2 -> 698588a — commits: 9b6f9c9 "update int"; no tags; Cargo.toml not present at both SHAs.
  • lib/rain.interpreter: 08ba136 -> ff1d064 — commits: cfbe0300 "static", adf58e9d "lint", 9eceb8fe "lint", 49b0bf68 "pointres", 98c1bc06 "lint", 69f49db0 "fix div", 9489dff6 "fix pointers", 4d51e949 "bump int"; no tags; Cargo.toml not present at both SHAs.

• Automated breaking/security keyword scan failed due to a regex escape error; commit messages contain "fix" and "bump int" which could be non-breaking but require manual review to confirm no API or security impact.

Action required: provide a short upstream-change summary for each updated submodule (what changed at the new SHAs), explicitly confirm there are no breaking API or security-impacting changes (or point to the upstream commits that do), and update CI to run:
git submodule sync --recursive && git submodule update --init --recursive --depth=1
Consider pinning these submodules to annotated tags if available.

lib/rain.interpreter (1)

1-1: Submodule bump — confirm upstream changes, ABI/license/security, and ensure CI uses recursive submodules

• lib/rain.interpreter -> repo: rainlanguage/rain.interpreter; BASE=08ba13647307e79dc9b98dc4f02d5f42e694199d → NEW=ff1d064d8fef013d17934694b59aecafad8409b9 (Merge PR Specify number of block confirmations to wait for a transaction per chain via config #405 "2025-09-16-float", 2025-09-17T17:29:37Z). Compare: +9 commits; changed files include generated pointer contracts, src/lib/op/math/LibOpDiv.sol and tests (test/src/lib/op/math/*).
• The submodule brings many nested submodules (rain.interpreter.interface, rain.lib.memkv, rain.metadata, rain.string, sol.lib.binmaskflag, plus nested forge-std/openzeppelin/etc.) — these are part of this bump.
• Actions required: review the upstream commit diffs for ABI/API, license, or security impacts (float/math additions may introduce ABI or behavior changes); ensure CI clones/updates submodules with --recursive and runs the affected tests (git submodule update --init --recursive or equivalent); repeat these checks for any other bumped submodules.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get the total diff stats for this PR to confirm the scope
git diff --stat HEAD~1..HEAD
# Also check what files were actually modified
git diff --name-only HEAD~1..HEAD

Length of output: 385

---

🏁 Script executed:

#!/bin/bash
# Check the current branch and commits
git branch -a
git log --oneline -5

# Get the diff stats for the PR by comparing against the target branch
git diff --stat origin/main..HEAD

# Check what files were modified
git diff --name-only origin/main..HEAD

Length of output: 145

---

🏁 Script executed:

#!/bin/bash
# Get the actual PR branch name and check its changes
git branch -r | grep 2025-09-16-exponent-overflow

# Try to get the diff against main for this PR
git fetch origin
git diff --stat origin/main...HEAD

# Get the list of changed files
git diff --name-only origin/main...HEAD

# Also try to see the submodule changes specifically
git diff origin/main...HEAD -- .gitmodules
git submodule status

Length of output: 316

---

🏁 Script executed:

#!/bin/bash
# Check the actual commit history and changes
git log --oneline --graph -10

# Check if there are any actual file changes beyond submodules
git show --name-only HEAD

# Get the diff stats for the latest commit
git show --stat HEAD

# Check what the actual changes are in the submodules
git show HEAD

Unrecoverable error: Sandbox execution failed: max_buffer, terminated

---

Based on the information available from the PR objectives and AI summary, I can assess this PR:

SIZE=S

---

🧠 Learnings used

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:24:42.275Z
Learning: For PR #1884, after each commit review, I should provide a new comment with a PR size report in the format: `TOTAL=number ADDITIONS=number DELETIONS=number`, excluding irrelevant files such as lock files (package-lock.json, cargo.lock, etc.).

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:24:42.275Z
Learning: After each commit in PR #1884, I should provide a new comment with the PR size report in the format: `TOTAL=number ADDITIONS=number DELETIONS=number`. The report should exclude irrelevant files such as lock files (e.g., package-lock.json, cargo.lock).

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:25:47.873Z
Learning: After each new commit review for rainlanguage/rain.orderbook repository, generate a PR size report in a separate comment with the format: "TOTAL=number ADDITIONS=number DELETIONS=number". This report should exclude irrelevant files such as lock files (e.g., package-lock.json, cargo.lock).

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:25:47.873Z
Learning: After each new commit review for rainlanguage/rain.orderbook repository, generate a PR size report in a separate comment with the exact format: "TOTAL=number\nADDITIONS=number\nDELETIONS=number". This report should exclude irrelevant files such as lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, cargo.lock).

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T22:14:22.646Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, I must consistently report the PR size after EVERY new commit in the exact format "TOTAL=number\nADDITIONS=number\nDELETIONS=number" without any formatting blocks. The report must exclude lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, cargo.lock) and can be included either as part of the review or as a separate comment.

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T22:14:22.646Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, I must consistently report the PR size after EVERY new commit in the exact format "TOTAL=number\nADDITIONS=number\nDELETIONS=number" without any additional text or formatting blocks. The report must exclude lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, cargo.lock) and can be included either as part of the review or as a separate comment.

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T22:46:08.530Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, the PR size report should be the only content in the comment - no text before it, no text after it, no formatting blocks, just the raw report in the exact format: "TOTAL=number\nADDITIONS=number\nDELETIONS=number". The report must exclude lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, cargo.lock).

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:24:53.708Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, provide a separate comment after each review with PR size statistics in the format: `TOTAL=number ADDITIONS=number DELETIONS=number`, excluding lock files like package-lock.json and cargo.lock.

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:24:53.708Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, provide a separate comment after each review with PR size statistics in the format: `TOTAL=number ADDITIONS=number DELETIONS=number`, excluding lock files like package-lock.json and cargo.lock.

---

Learnt from: rouzwelt
PR: rainlanguage/rain.orderbook#0
File: :0-0
Timestamp: 2025-05-21T21:24:53.708Z
Learning: For PR #1884 in rainlanguage/rain.orderbook, provide a separate comment after each review with PR size statistics in the format: `TOTAL=number ADDITIONS=number DELETIONS=number`, excluding lock files like package-lock.json and cargo.lock.