feat(dashmate): add core reindex command

[pshenmic]

Issue being fixed or feature implemented

Sometimes, dashcore nodes require reindex (rescan of blockchain) in order to recover or find missing transactions.

When you are using standalone dashcore, you have to manually edit dashcore configuration files and run nodes in reindex mode. Then get it back after the operation succeeded.

Using dashmate, we run everything in docker and it is hard to achieve that without dropping the whole chain and messing with containers. To accomplish that, you need to edit templates, and do some tricky stuff.

What was done?

Added new command reindex for both regular and local configurations, which runs core nodes from your configuration in the reindex mode. It modifies the configuration of dashcore, start the core, wait until it finishes sync, and turn configuration back again.

Implementation Details

New configuration keys are introduced in the config: core.reindex, core.reindexContainerId. When reindex command is called, it sets core.reindex to 1, which renders new dash.conf file in your dashmate folder, and start the core via startCore function. Container id of started container saved in the configuration under core.reindexContainerId path. It is used for the command interruption. You can ctrl + c any time, it will pick up container next run. Then the command will connect to the core and wait until the blockchain is fully synced. Once dashcore reach the head of blockchain, the command will stop it back, and reset core mode back to 0.

You cannot start configartion until resync is fully complete

How Has This Been Tested?

Locally

Breaking Changes

• Added new required core.reindex and optionsl core.reindexContainerId configuration key

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[lgtm-com]

This pull request introduces 5 alerts when merging 397a456 into 0102380 - view on LGTM.com

new alerts:

• 3 for Unused variable, import, function or class
• 2 for Missing variable declaration

[lgtm-com]

This pull request introduces 5 alerts when merging 0ca2433 into 0102380 - view on LGTM.com

new alerts:

• 3 for Unused variable, import, function or class
• 2 for Missing variable declaration

[lgtm-com]

This pull request introduces 2 alerts when merging 1a27d86 into dbf3560 - view on LGTM.com

new alerts:

• 2 for Missing variable declaration

[shumkov]

👍

[shumkov]

👆

[lgtm-com]

This pull request introduces 2 alerts when merging 47e46f7 into dbf3560 - view on LGTM.com

new alerts:

• 2 for Missing variable declaration

[lgtm-com]

This pull request introduces 3 alerts when merging 60edd37 into dbf3560 - view on LGTM.com

new alerts:

• 2 for Missing variable declaration
• 1 for Overwritten property

[lgtm-com]

This pull request introduces 3 alerts when merging a7edbfc into dbf3560 - view on LGTM.com

new alerts:

• 2 for Missing variable declaration
• 1 for Overwritten property

[lgtm-com]

This pull request introduces 3 alerts when merging c4d855a into dbf3560 - view on LGTM.com

new alerts:

• 2 for Missing variable declaration
• 1 for Overwritten property

[shumkov]

Good job! 👍