This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
WIP safe mode and tx pause {continued} #12371
Merged
Merged
Changes from 19 commits
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
d076c92
progress on true call UI types
nuke-web3 1f2a727
mid rework progress on tx pause
nuke-web3 bf9c803
stck on overflow evaluating the requirement `pallet::Call<mock::Test>…
nuke-web3 427d48b
tests pass, kitchen sink needs proper impl for origins
nuke-web3 a8f06db
fmt
nuke-web3 04a4711
UnfilterableCalls uniform naming
nuke-web3 55b38bb
Fix safe-mode benchmarks
ggwpez 7aad890
Fix safe-mode benchmarks
ggwpez 354a251
fix build errors, except origin issue
nuke-web3 80ede09
update to use named parameter syntax for Events
nuke-web3 cd50d92
building
nuke-web3 ed6c25f
building except wasm runtime
nuke-web3 36ee207
benchmarking::bench_force_activate' has overflowed its stack
nuke-web3 1b6b2b8
??? enum shit
nuke-web3 d7c7130
benchmark tests passing
nuke-web3 ac9020d
named reserve impl, tests pass
nuke-web3 5d78e1d
test coverage safe mode
nuke-web3 f2f9435
weights.rs for safe mode and tx pause dummy files configured
nuke-web3 917961b
Fix benchmarks overflow
ggwpez f1daf3c
names, more comments safe-mode
nuke-web3 6bfff58
move back to stringy function inputs, with check on validity
nuke-web3 cc490ae
safe-mode fmt
nuke-web3 73225ce
broken?
nuke-web3 b95b286
tests passing, use FullNameOf to check tx-pause unfilterables
nuke-web3 bbe4ee5
add proxy and utility pallets to mock tx pause
nuke-web3 163ea73
safe-mode and utility and proxy in mock and tests
nuke-web3 adb3ab8
tests for proxy and utility for safe mode
nuke-web3 0538ecd
tests for proxy and utility for tx-pause, fmt
nuke-web3 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will prefer to make it
so that frontend doesn't need to hardcod those number once more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool - TIL https://doc.rust-lang.org/reference/items/enumerations.html#custom-discriminant-values-for-fieldless-enumerations is a thing
So this example diff works to yield an integer castable item, so BlockNumber works fine.
But you cannot assign the same value for any origin this way as it would conflict:
I think this restriction would be OK, but hope there is a better method to get there... Open to ideas.