fix: validate Supabase fields independently (M3)#93
fix: validate Supabase fields independently (M3)#930x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
When a Supabase row had one invalid field (dex_pool_address or mainnet_ca failing base58 validation), the `continue` discarded the entire row — including the other valid field. A HYPERP market with a corrupted mainnet_ca but valid dex_pool_address lost its pool address. Validate each field independently: null out only the invalid field and always store the row in dbMarkets with whichever fields are valid. 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 5 minutes and 5 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 |
1 participant
Summary
continuewhich discarded the entire row when one field failed base58 checkdex_pool_addressbut corruptedmainnet_calost its pool addressundefined, valid sibling is preservedTest plan
🤖 Generated with Claude Code