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

Socket not sending queueid back with response #659

Closed
lukechilds opened this issue Mar 9, 2018 · 8 comments
Closed

Socket not sending queueid back with response #659

lukechilds opened this issue Mar 9, 2018 · 8 comments

Comments

@lukechilds
Copy link
Contributor

lukechilds commented Mar 9, 2018

I may be misunderstanding how the queueids were supposed to work, but it was my understanding we could send an HTTP request with a non zero queueid and the socket would send a message when it had been processed with the corresponding queueid attached so we could match it up to the request.

However I don't seem to be getting a queueid property on any of the socket messages responding to HTTP calls.

e.g sending:

{"queueid":2,"method":"electrum","coin":"KMD","ipaddr":"electrum1.cipig.net","port":10001}

I get the following response over the socket:

{"ipaddr":"electrum1.cipig.net","port":10001,"result":"success"}

Also, we're getting the invalid ending char on these messages like we had on the other messages before. Are you able to remove the ending char and add the queueid to the response so we can pair them up with the requests?

Built mm from latest commit in dev branch: 207238f

@jl777
Copy link
Owner

jl777 commented Mar 9, 2018

it seems I goofed up some git merge and it reverted some changes.
added them back, plz try again

@lukechilds
Copy link
Contributor Author

lukechilds commented Mar 13, 2018

Apologies for delay, just checked this and although you are now passing back a queueid you seem to passing it back inside the result object

e.g I'm now getting:

{"queueid":0,"result":{"queueid":2,"method":"electrum","coin":"KMD","ipaddr":"electrum1.cipig.net","port":10001}}

When I think it should be:

{"queueid":2,"result":{"method":"electrum","coin":"KMD","ipaddr":"electrum1.cipig.net","port":10001}}

@lukechilds
Copy link
Contributor Author

lukechilds commented Mar 13, 2018

I've just noticed, since that fix you seem to be passing back the original request rather than the response.

@lukechilds
Copy link
Contributor Author

Correct response should be:

{"queueid":2,"result":{"ipaddr":"electrum1.cipig.net","port":10001,"result":"success"}}

@jl777
Copy link
Owner

jl777 commented Mar 13, 2018

sorry about that. have no idea how I could have messed that up so bad. pushed fix to jl777 branch

@lukechilds
Copy link
Contributor Author

Haha, soooo close, but now the invalid ending char has creeped back in. Are you able to trim that off? Then we should be sorted 🍾

{"queueid":2,"result":{"ipaddr":"electrum1.cipig.net","port":10001,"result":"success"}}�

@jl777
Copy link
Owner

jl777 commented Mar 14, 2018

pushed fix

@lukechilds
Copy link
Contributor Author

Resolved, thanks.

DeckerSU pushed a commit to DeckerSU/SuperNET that referenced this issue Nov 5, 2022
Sync conf settings between trading nodes. Add conf settings to buy/sell/setprice. Increase locktimes for notarized swaps by 4x. Reduce BTC swaps locktimes to 4x from 10x.
jl777#568
jl777#659
jl777#660

* WIP.

* WIP.

* WIP. Added tests for choose_maker_confs_and_notas and choose_taker_confs_and_notas.

* WIP. Not compiling.

* Add integration tests. Use TakerRequestBuilder in lp_auto_buy.

* Sleep for 3 seconds to be sure that Started event is saved.

* Detect locktime version and use 4x locktime for notarized swaps.

* Fix lock time selection when 1 node requires nota and other does not.

* Fix lock time selection when nodes end up syncing conf settings w/out notas.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants