Skip to content
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

Setup Private Testnet --create-genesis-json creates witness_node_data_dir #1118

Closed
6 tasks
cedar-book opened this issue Jul 4, 2018 · 6 comments
Closed
6 tasks
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 5b Docs In Progress Status specific to Documentation indication they are currently being refined 9a Tiny Effort estimation indicating TBD bug

Comments

@cedar-book
Copy link

cedar-book commented Jul 4, 2018

Setup Private Testnet --create-genesis-json creates witness_node_data_dir

  • Windows 10 (64-bit)
  • WSL environment

Testing setup [Private Testnet steps] (https://dev.bitshares.works/en/master/development/testnets/private_testnet.html)

(step 3) When I run ./witness_node --create-genesis-json=my-genesis.json, creating a "my-genesis.json" and also "witness_node_data_dir" folder.

private-testnet-setup-1

It seems... go to main.cpp and check the "witness_node_data_dir" and "create_new_config_file()".
How can I stop this? Because (step 6) Creates a "data" Directory and also config.ini in it.

private-testnet-setup-2

private-testnet-setup-3

Impacts

  • [x ] Setup Private Testnet Data directory structure

** Installation **
Followed: https://dev.bitshares.works/en/master/development/installation/build_ubuntu.html

  • BitShares Core Release 2.0.180612

CORE TEAM TASK LIST

  • Evaluate / Prioritize Bug Report
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@cedar-book
Copy link
Author

I checked a witness_node executable main() for a part of another issue and created a code flow (in page 8) to view the flow.

You may or may not have own data directory that does not matter. If --data-dir is not set in a command line when witness_node starts (and not find a config.ini), a witness_node_data_dir will be created (if not exists). So, if you create own data directory and forget to set the --data-dir when you start a witness_node, you get new default data directory and config.ini to start the witness_node.

@abitmore, I can think about two options. (1) update the logic or (2) in the documentation clearly mention (warn) to users; you have to define a data directory if you have own data directory (with config.ini), otherwise, witness_node_data_dir will be created and used a default config.ini.
Because of the config.ini, thought that might be better not to create an extra data directory. But we can do only the option (2). or something else?

@abitmore
Copy link
Member

abitmore commented Jul 9, 2018

You may or may not have own data directory that does not matter. If --data-dir is not set in a command line when witness_node starts (and not find a config.ini), a witness_node_data_dir will be created (if not exists). So, if you create own data directory and forget to set the --data-dir when you start a witness_node, you get new default data directory and config.ini to start the witness_node.

Correct.

(2) in the documentation clearly mention (warn) to users

Agreed.

@cedar-book
Copy link
Author

cedar-book commented Jul 10, 2018

Added Note and Warning in a Private Testnet page. @abitmore, please review. This is the information how it was updated.
(updated links: 2019-2-1)

@abitmore abitmore added bug 3d Bug Classification indicating the existing implementation does not match the intention of the design 9a Tiny Effort estimation indicating TBD labels Aug 17, 2018
@ryanRfox
Copy link
Contributor

ryanRfox commented Feb 1, 2019

I believe this may already be resolved, but going to add it to the next Feature Release so we test it out and validate our documentation. Here is the current Private Testnet Setup page.

@ryanRfox ryanRfox added the 5b Docs In Progress Status specific to Documentation indication they are currently being refined label Feb 1, 2019
@abitmore
Copy link
Member

abitmore commented Feb 1, 2019

I don't think we've worked on this issue.

@pmconrad
Copy link
Contributor

pmconrad commented Feb 4, 2019

Resolved by #1529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3d Bug Classification indicating the existing implementation does not match the intention of the design 5b Docs In Progress Status specific to Documentation indication they are currently being refined 9a Tiny Effort estimation indicating TBD bug
Projects
None yet
Development

No branches or pull requests

4 participants