Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

Problem: v0.5.x client-cli cannot sync #1552

Closed
calvinlauyh opened this issue May 6, 2020 · 1 comment
Closed

Problem: v0.5.x client-cli cannot sync #1552

calvinlauyh opened this issue May 6, 2020 · 1 comment
Labels
client-cli

Comments

@calvinlauyh
Copy link
Contributor

Describe the bug
When trying to sync a wallet with client v0.5.x (including master), the client-cli returns with

Error: Initialization error: Unable to initialize sled storage at path: .storage

To Reproduce
Steps to reproduce the behavior:

  1. Build on release or master branch
  2. Create/restore a wallet
  3. Run ./client-cli sync --name Wallet
  4. See error

Expected behavior
Expected the synchronization should start working

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: MacOS, Ubuntu 18.04
  • Version: v0.5.x, master
@lezzokafka
Copy link
Collaborator

Note: v0.4 release works fine.

tomtau added a commit to tomtau/chain that referenced this issue May 7, 2020
@tomtau
Problem: v0.5.x client-cli cannot sync (fixes crypto-com#1552)
9ba1761 
Solution: storage opened only once
@tomtau tomtau mentioned this issue May 7, 2020
Closed
bors bot added a commit that referenced this issue May 7, 2020
@bors @tomtau
Merge #1553
3fd0856 
1553: Problem: v0.5.x client-cli cannot sync (fixes #1552) r=tomtau a=tomtau

Solution: storage opened only once


Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
tomtau added a commit that referenced this issue May 7, 2020
@tomtau
Problem: v0.5.x client-cli cannot sync (fixes #1552)
c227cbd 
Solution: storage opened only once

(cherry-picked c0ec378)
@bors bors bot closed this as completed in c0ec378 May 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
client-cli
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@calvinlauyh @lezzokafka