Fix --preimage storage value
#675
Closed
Conversation
This file contains 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
|
dry-run-preimage works fine. what are you trying to fix? |
|
ok I see. in your case it didn't work because compactAddLength returns u8a and your using rpc method |
|
Oh, I see. Sorry, I didn't realize. Ok. I'll close the PR then. |
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.
Related to: #630 and paritytech/polkadot-sdk#3522
I'm trying to simulate some bridge-initialization calls using chopsticks. I used the code found in
dry-run-preimage.tsas an example for crafting my owndev_setStoragecall for simulating an approved preimage. The initial version didn't work (it was failing withCallUnavailable) and it took quite a while to find the solution presented in #630. Not sure if this is the best fix, but I think it would bring value to have this fixed. At least it would have saved a lot of time for me.