-
Notifications
You must be signed in to change notification settings - Fork 649
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
set default quote asset_id to 1.3.1 #1132
Conversation
In current help message of create_asset, printed in gethelp, gives an example of option with quote asset_id of "1.3.0". This asset id is not a valid one, since the code requires the id to be "1.3.1" on creating a new asset. This change set the default quote asset_id to "1.3.1", so that the gethelp message would give a valid option example.
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.
Makes sense.
Make sure all test cases pass and can successfully sync the chain, then we can merge it.
Thanks.
I have tried command create_asset and update_asset in cli_wallet. Not sure how to run all the test cases? |
run all the tests with:
make sure you end up with also, start a witness node with your changes and synchronize the chain, i understand you are making the change for a cli wallet command but your change is done in the core(asset_ops file) so we need to make sure this does not break anything. |
sure, I will run the test and paste the result. BTW, I don't need to sync all the data by running the witness_node, right? Since my machine doesn't hold much memory. Is "Get block..." a symbol for the validation? |
The chain_test result is: *** No errors detected And I start a witness_node to connect my testnet(without this change), the console log shows getting a block successfully.
|
Also I tried to connect to the mainnet, below is the console log:
|
by default the node will require around 20 gigs of ram, by using |
ok, I will schedule the test at the weekend. Not sure how many I could sync. |
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 just synced with your code up to 2017-06. i think this will cause no harm.
Thanks for merging this commit. BTW, I am willing to know how to make sure the code works fine? For example, currently I synced block till 2018-03-18.
Is this a proof for the code is fine? Do we need other evidence? |
Currently, it synced to 2081-07-04
And took 9.6G ram by running the witness_node with --max-ops-per-account 10 set.
Not sure how many more it could sync. |
I think it is synced with current network and processing transactions.
|
thanks @RichardWeiYang thats good enough for this. very appreciated. |
In current help message of create_asset, printed in gethelp, gives an
example of option with quote asset_id of "1.3.0". This asset id is
not a valid one, since the code requires the id to be "1.3.1" on
creating a new asset.
This change set the default quote asset_id to "1.3.1", so that the
gethelp message would give a valid option example.