Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
691: display call stack for unsuccessful unsafe calls r=piotr-iohk a=KtorZ # Issue Number <!-- Put here a reference to the issue this PR relates to and which requirements it tackles --> # Overview <!-- Detail in a few bullet points the work accomplished in this PR --> - [x] I have added "stack traces" for unsafe calls when they fail. # Comments <!-- Additional comments or screenshots to attach if any --> It's not much, but it turns: ``` uncaught exception: ErrorCall TextDecodingError {getTextDecodingError = "Unable to decode Address: encoding is neither Bech32 nor Base58."} CallStack (from HasCallStack): error, called at src/Cardano/Wallet/Unsafe.hs:56:13 in cardano-wallet-core-2019.7.24-vtyOM1MPP4BB3M0K9gXCg:Cardano.Wallet.Unsafe ``` into ``` uncaught exception: ErrorCall TextDecodingError {getTextDecodingError = "Unable to decode Address: encoding is neither Bech32 nor Base58."} CallStack (from HasCallStack): error, called at src/Cardano/Wallet/Unsafe.hs:58:13 in cardano-wallet-core-2019.7.24-vtyOM1MPP4BB3M0K9gXCg:Cardano.Wallet.Unsafe unsafeDecodeAddress, called at test/unit/Cardano/Wallet/Jormungandr/CompatibilitySpec.hs:121:21 in main:Cardano.Wallet.Jormungandr.CompatibilitySpec ``` which makes it easier to locate the point of failure. <!-- Don't forget to: ✓ Self-review your changes to make sure nothing unexpected slipped through ✓ Assign yourself to the PR ✓ Assign one or several reviewer(s) ✓ Once created, link this PR to its corresponding ticket ✓ Acknowledge any changes required to the Wiki --> Co-authored-by: KtorZ <matthias.benkort@gmail.com>
- Loading branch information