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

Wrong verification #900

Closed
offerm opened this issue Apr 18, 2019 · 1 comment · Fixed by #901
Closed

Wrong verification #900

offerm opened this issue Apr 18, 2019 · 1 comment · Fixed by #901
Assignees
Labels
bug Something isn't working

Comments

@offerm
Copy link
Contributor

offerm commented Apr 18, 2019

From the bot log on test1:

Trying to place an order immediately after xud restart gives this error and the bot gives up on order placing.

2019/04/18 06:55:23 [ERROR] Lost connection to XUD. Retrying in 5 seconds
2019/04/18 06:55:28 [INFO] version:"1.0.0-alpha.11" node_pub_key:"02b66438730d1fcdf4a4ae5d3d73e847a272f160fee2938e132b52cab0a0d9cfc6" num_pairs:2 orders:<> lnd:<key:"BTC" value:<channe
ls:<active:2 pending:1 > chains:"bitcoin" blockheight:259153 version:"0.5.0-beta commit=v0.4.2-beta-1254-g13afd0b4de30c2ddb752b0095fcda3e53c01fc7e" alias:"LND for BTC on 10002/10012" >
 > lnd:<key:"LTC" value:<channels:<active:2 > chains:"litecoin" blockheight:472387 version:"0.5.0-beta commit=v0.4.2-beta-1254-g13afd0b4de30c2ddb752b0095fcda3e53c01fc7e" alias:"LND for
 LTC on 10001/10011" > > raiden:<address:"0x7ed0299Fa1ADA71D10536B866231D447cDFa48b9" > 
2019/04/18 06:55:28 [DEBUG] Placing orders
2019/04/18 06:55:28 [DEBUG] Subscribing to order events
2019/04/18 06:55:28 [DEBUG] Placing order: {0.0077 350000000 LTC/BTC  BUY} 
2019/04/18 06:55:28 [ERROR] Could not place orders: {0.0077 350000000 0} - rpc error: code = Unknown desc = LTC does not have sufficient outbound balance of: 350000000

However, if you restart the bot, everything works fine.

@offerm offerm added the bug Something isn't working label Apr 18, 2019
@offerm offerm assigned ghost and sangaman Apr 18, 2019
@sangaman
Copy link
Collaborator

I think I see the issue and am working on a fix.

sangaman added a commit that referenced this issue Apr 18, 2019
This fixes a bug where the capacity for swap clients is thought to be 0
upon initialization. The checks to update the capacity happen on an
interval but not right away. This adds logic to check the capacity
immediately.

Fixes #900.
sangaman added a commit that referenced this issue Apr 18, 2019
This fixes a bug where the capacity for swap clients is thought to be 0
upon initialization. The checks to update the capacity happen on an
interval but not right away. This adds logic to check the capacity
immediately.

Fixes #900.
sangaman added a commit that referenced this issue Apr 18, 2019
This fixes a bug where the capacity for swap clients is thought to be 0
upon initialization. The checks to update the capacity happen on an
interval but not right away. This adds logic to check the capacity
immediately.

Fixes #900.
sangaman added a commit that referenced this issue Apr 18, 2019
This fixes a bug where the capacity for swap clients is thought to be 0
upon initialization. The checks to update the capacity happen on an
interval but not right away. This adds logic to check the capacity
immediately.

Fixes #900.
@ghost ghost added the in progress label Apr 18, 2019
@kilrau kilrau added this to the 1.0.0-sprint.14 milestone Apr 20, 2019
@kilrau kilrau unassigned ghost Apr 20, 2019
@ghost ghost removed the in progress label Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants