-
Notifications
You must be signed in to change notification settings - Fork 20
fix: dryRun check + fix multiple solutions bug
#443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
7afda4a
7efd8dc
f048c1f
895aabc
7abc4e1
d7f00bc
2fbaee1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -223,6 +223,13 @@ pub struct MonitorConfig { | |
| /// configured, it might re-try and lose funds through transaction fees/deposits. | ||
| #[clap(long, short, env = "SEED")] | ||
| pub seed_or_path: String, | ||
|
|
||
| /// Verify the submission by `dry-run` the extrinsic to check the validity. | ||
| /// If it fails then the block is ignored. | ||
|
||
| /// | ||
| /// This requires a RPC endpoint that exposes unsafe RPC methods. | ||
| #[clap(long)] | ||
| pub dry_run: bool, | ||
| } | ||
|
|
||
| #[derive(Debug, Clone, Parser)] | ||
|
|
||
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.
if we got back
method not foundis most likely because the RPC method was unsafe, then just terminate.all solutions will be rejected anyway then