-
Notifications
You must be signed in to change notification settings - Fork 515
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
submitAndWait
in standalone mode
#2478
Comments
Is this necessary when you can just use |
Is it known that submitAndWait does not work with a ledger_accept call? In our initial testing, it seems running ledger_accept from the command line interface seems to unblock the submitAndWait call, where calling it via ws or rpc does not. We built some code into a library using submitAndWait, and wanted to test it against a stand-alone rippled service. If submitAndWait is a supported function, it seems odd that it wouldn't be testable in this way. |
Alternatively, you can also just do a basic
|
We cannot use
submitAndWait
in a standalone mode network.I propose to add a standalone flag to the submitAndWait parameter so that the
ledger_accept
command can be executed in the process.Ideally, it should be able to run in stand-alone mode and on other testnets with nearly identical simple code, although it is possible to do so in other ways.
The text was updated successfully, but these errors were encountered: