test: follow-up #6762 and #6763 to remove workaround and fix error message#6790
test: follow-up #6762 and #6763 to remove workaround and fix error message#6790PastaPastaPasta merged 1 commit intodashpay:developfrom
Conversation
✅ No Merge Conflicts DetectedThis PR currently has no conflicts with other open PRs. |
WalkthroughThe changes modify the error handling and wallet unlocking behavior in the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📥 CommitsReviewing files that changed from the base of the PR and between 2c08506c123d433c05edd6c33c7f3189edd00e5e and 4dca765. 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
…remove workaround and fix error message 4dca765 test: follow-up dashpay#6762 - removed related TODO from functional test (Konstantin Akimov) Pull request description: ## Issue being fixed or feature implemented Once both dashpay#6762 and dashpay#6763 are merged, no more need to have a workaround with manual lock / unlock of descriptor wallet before `upgradetohd`. I fixes CI failure on develop also due to conflict. ## What was done? Removed this workaround from `wallet_upgradetohd.py` ## How Has This Been Tested? See CI ## Breaking Changes N/A ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone ACKs for top commit: DashCoreAutoGuix: utACK 4dca765 (used wrong account, disregard) PastaPastaPasta: utACK 4dca765 kwvg: utACK 4dca765 Tree-SHA512: 435359f53f42c29f3e6885ab6fbeabd1a31135fe67a15b894e6f4a92a0aced3e96e0f1bb38598eb74eb251df1f6ae603e033ee41e3bf500bcc4d6c5c1031b800
Issue being fixed or feature implemented
Once both #6762 and #6763 are merged, no more need to have a workaround with manual lock / unlock of descriptor wallet before
upgradetohd.I fixes CI failure on develop also due to conflict.
What was done?
Removed this workaround from
wallet_upgradetohd.pyHow Has This Been Tested?
See CI
Breaking Changes
N/A
Checklist: