chore: update rust-dashcore dependency to store TransactionContext in TransactionRecord#3406
chore: update rust-dashcore dependency to store TransactionContext in TransactionRecord#3406dashinfraclaw wants to merge 1 commit intodashpay:v3.1-devfrom
Conversation
|
Warning Rate limit exceeded
⌛ 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. 📝 WalkthroughWalkthroughUpdated the git revision for six Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
… TransactionRecord Update dashcore/dashcore-rpc git dependencies to 5114330ae564858803d656efba84bb4adacb2a2e for integration testing of dashpay/rust-dashcore#582.
6ea48cd to
ad5c132
Compare
|
Already working #3405 |
Issue being fixed or feature implemented
Automated integration test for dashpay/rust-dashcore#582.
Validates that the changes in rust-dashcore PR #582 (
refactor: store TransactionContext in TransactionRecord) compile and pass CI against this repository.What was done?
Updated all
dashcore/dashcore-rpcgit dependencies in Cargo.toml files to point at the PR HEAD commit (5114330ae564858803d656efba84bb4adacb2a2e).No functional code changes — dependency pointer update only.
How Has This Been Tested?
This PR exists to run the repository's existing CI suite against the updated dependency. CI results on this PR directly indicate compatibility.
Breaking Changes
None introduced by this PR. Any CI failures indicate potential breaking changes in the upstream rust-dashcore PR.
Checklist:
Summary by CodeRabbit