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

Rescan always starting at block 0 (REST) #313

Closed
MrGoro opened this issue Sep 14, 2017 · 3 comments
Closed

Rescan always starting at block 0 (REST) #313

MrGoro opened this issue Sep 14, 2017 · 3 comments
Assignees
Labels
bug Unexpected or incorrect behavior

Comments

@MrGoro
Copy link

MrGoro commented Sep 14, 2017

I'm trying to init a rescan of the walletdb with a specifiy height.

From the Wallet Admin Docs i find two differnet types of requests that should init the same rescan. But when I use those request according to my debug.log the rescan always start at block 0.

My requests:
curl http://my-bcoin-node.com:8332/wallet/_admin/rescan -X POST '{"height": 481000}'
curl http://my-bcion-node.com:8332/wallet/_admin/rescan?height=481000 -X POST
(Basic Auth is left out but as the rescan starts - although at 0 height - i asume that this is not the problem)

Version: v1.0.0-beta.14

Maybe you can tell me if this is an issue or if I'm doing something wrong. Thanks!

@bucko13
Copy link
Contributor

bucko13 commented Sep 19, 2017

Ugh, pain to debug since you have to wait for it to rescan if entered incorrectly. One thing is to make sure to pass the body via the --data argument. i.e. --data '{"height": 481000}'. I did do that though and mine also started at 0 so we'll have to take a closer look.

@bucko13 bucko13 added the bug Unexpected or incorrect behavior label Oct 10, 2017
@bucko13 bucko13 added the bug Unexpected or incorrect behavior label Nov 21, 2017
@nodech
Copy link
Member

nodech commented Nov 22, 2017

With current master I can't replicate the problem. I guess it was fixed?

command:

curl $url/wallet/_admin/rescan \
  -X POST \
  --data '{"height": '$height'}'

@MrGoro @bucko13

@bucko13
Copy link
Contributor

bucko13 commented Nov 23, 2017

Closing for now! Let us know if it comes back.

@bucko13 bucko13 closed this as completed Nov 23, 2017
@bucko13 bucko13 added the bug Unexpected or incorrect behavior label Apr 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or incorrect behavior
Projects
None yet
Development

No branches or pull requests

3 participants