Sync node always starts from the catchup
A pull request for this has already been merged.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
Sync node by default downloads the snapshot after init
Also, sync node has an ability to run repair from the snapshot
Versions
node-cli: 2.6.0
Preconditions:
Active chain medium type
Instance with whitelisted IP
To Reproduce
- Run
skale sync-node init init-env - Check Skaled logs
- Run
skale sync-node repair - Check Skaled logs
Expected behavior
Skaled should start from the snapshot after 1st and 3rd steps
Actual state
Skaled always starts from the catchup
- Dominant language
- Python
- Stars
- 21
- Forks
- 7
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from skalenetwork/node-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
skalenetwork/node-cli#842 ·
-
skalenetwork/node-cli#946 · 1 assignee ·
-
skalenetwork/node-cli#941 · 2 comments · 1 assignee ·
-
fair-node
skalenetwork/node-cli#938 · 1 assignee ·
-
skalenetwork/node-cli#934 · 1 assignee ·
All issues in skalenetwork/node-cli
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100