Skip to content

fix(prism-lium): hard-reject multi-GPU offers for single-GPU rent - #129

Merged
echobt merged 1 commit into
mainfrom
fix/prism-lium-single-gpu
Aug 12, 2026
Merged

fix(prism-lium): hard-reject multi-GPU offers for single-GPU rent#129
echobt merged 1 commit into
mainfrom
fix/prism-lium-single-gpu

Conversation

@echobt

@echobt echobt commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Prism Lium provisioning previously accepted any offer with gpu_count >= requested and, on host-split failures, retried rent with the offer’s full GPU count — so 8× RTX 5090 hosts could be selected/billed when the spec asked for .
  • Hard-reject multi-GPU offers (numeric count and 8x / / x8 labels); prefer exact single-GPU 5090; never rent more GPUs than InstanceSpec.gpu_count.
  • Unit tests: 1×5090 wins over cheaper 8×5090; all-multi catalogs yield NoCapacity.

Test plan

  • cargo test -p prism-lium-types --lib
  • cargo test -p prism-lium --lib
  • cargo clippy -p prism-lium-types -p prism-lium --all-targets -- -D warnings
  • CI green
  • After merge: deploy prod prism-challenge image before relaunching affected miner submission

Offer selection used gpu_count >= requested and fell back to renting the
host's full GPU count on split failures, so 8×5090 hosts could be billed.
Filter to exact single-GPU matches (including 8x/x8 labels) and never rent
more GPUs than the spec asks for.
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 27 minutes

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a6df7fd9-8c1f-46d1-9276-93963c0fe593

📥 Commits

Reviewing files that changed from the base of the PR and between 7441dcf and a1ee2a1.

📒 Files selected for processing (4)
  • crates/prism-lium-types/src/lib.rs
  • crates/prism-lium-types/src/types.rs
  • crates/prism-lium/src/client.rs
  • crates/prism-lium/src/lib.rs

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.

@echobt
echobt merged commit 86e47a8 into main Aug 12, 2026
4 checks passed
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