Restore fast delegated roll result handling - #124
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
WalkthroughThe delegated dice roll flow now centralizes completion and live-correlation decisions in shared helpers, tracks pending roll context, conditionally subscribes to callback logs, and adds focused unit-test coverage. ChangesDelegated roll reconciliation
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
sporicle
marked this pull request as ready for review
July 28, 2026 09:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
rollnumadvances after the signed request.Why
The current frontend makes callback logs primary and performs an additional account RPC before resolving the UI. That preserves correlation correctness but adds avoidable client-side latency after the player account has already changed. The older frontend reacted immediately to account notifications, but accepted any update and could associate stale or unrelated callbacks with the pending roll.
This restores the direct account-subscription path when an advancing
rollnumproves a new result, while preserving correlated fallbacks where account state alone is ambiguous.Impact
Ordinary delegated rolls resolve on the first valid account notification without extra live WebSocket subscriptions or an additional account fetch. Onchain VRF scheduling latency remains unchanged.
Validation
npm run test:roll-result(7 tests)npx tsc --noEmitnpm run buildSummary by CodeRabbit
Bug Fixes
Tests
Chores