Conversation
The CM wizard's createCollection method was missing plugin support (e.g. royalties). Now prompts the user to select and configure plugins when creating a collection through the wizard, using the same plugin selector and configurator as core collection create.
The guard parser used sol(lamports / 10**9) which produces a float for small values (e.g. 1 lamport → 1e-9) that can't convert to BigInt. Now uses lamports() directly since the input is already in lamports. Affects solPayment, botTax, freezeSolPayment, and solFixedFee guards.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 53 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
2 participants
Fix collection plugins and guard parsing in CM wizard