fix: fetch Supabase metadata on hot-register, report crank result (M4+M5)#94
Conversation
…(M4+M5) M4: registerMarket() did not query Supabase for dex_pool_address. HYPERP markets hot-registered via /register had no pool address until the next discover() cycle (5 min default), causing UpdateHyperpMark to be skipped. Now queries Supabase for the single market's metadata with base58 validation, matching the discover() pattern. M5: registerMarket() discarded crankMarket() return value and always reported success. Now captures the boolean and includes it in the response message so callers know if the initial crank succeeded. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
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 0 minutes and 25 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. ✨ 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 |
Summary
M4 — Missing Supabase metadata on hot-register:
registerMarket()never queried Supabase fordex_pool_address/registerhad no pool address for up to 5 min.eq("slab_address", ...)and validates with base58 regexdiscover()(lines 274-285)M5 — Crank result discarded:
crankMarket()return value was ignored, always reported successsuccess: true(market is tracked regardless), but message distinguishes crank success vs failureTest plan
🤖 Generated with Claude Code