-
Notifications
You must be signed in to change notification settings - Fork 44
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
Trading issue #612
Comments
I'll try to take a look at all of this tonight (or tomorrow at the latest), but |
Stumpled upon this independently and was just about to open an issue too, let's leave sorted/non sorted out here for now. It's about order execution not being correct:
|
@offerm the current behavior is that if xud finds non-internal match, and a swap is not supported ( We can reconsider this behavior, improve the logging, and add swap failures output (#609). |
I think we should keep the behavior, but more logging and returning swap failures on the grpc level might be helpful. I'm pretty sold that returning the swap failures is a good idea - we already have an issue for it - for logging we should already log the swap failures, but maybe we can also log something everytime we do |
There are several issues here: |
That's due to a bug in the |
@offerm the same bug created many problems. The fix was merged, let's test again. |
Using the latest master: started with 10 orders (5 buy, 5 sell)
Side note:
Impact:
so I guess this is why price 1.13 was done only 1 time and why these 2 orders are still there. IMHO we have to reduce the complexity or things and not implement mechanisms for which we are not sure about the need, The retry is a good example. why are we doing retry when we get a permanent error? at that time we could swap with another peer. Also, keep in mind the subject of this issue - it is the user and how he can understand what is going on.
the |
I opened #618 . -- We have 3 kind of results when placing an order:
The output that you suggest also includes:
Out stream method output is identical to the non-stream, but not aggregated. I'm not sure if we want to publish all these events - we can improve the logging instead. If others will endorse your format (@kilrau @sangaman @michael1011 ), we also need to decide on whether to have it in the non-stream version as well, which will make it more like the full scenario story, and not just the information that the client needs for processing. -- No output on your market order: -- Retry mechanism: -- I wasn't sure if there were more problems in what you described. Let me know if so. |
I like this general format for the output of the cli, I'll create an issue for that specifically. |
I'm not sure what the issue is with the retry logic? Retrying what exactly? Do you mean how we handle trying a different order when one order fails? |
Good, I like the format too - supportive! We might even save some events and just state starting swap directly after match, no need for a particular event here. |
@moshababo do we have a case for the retries? |
@offerm you mean the swaps retries? if so, what's the question about it? |
I don't want to make this issue more messy, here as a separate bug list which this issue should close: #638 |
Opened #639 for the retries. Closing this one |
Guys,
Assume that I'm an exchange that just installed XUD.
See what I did.
Can you please help me to explain what happened?
At startup I'm connected to LNDs and to 3 peers and have 11 peer orders. all good.
Looking at the orders I see BUY orders and SELL orders.
The sell orders are not sorted by price
trying to sell 0.003 at market. Expecting to take the first 2 BUY orders and part of the 3rd order
buy got nothing back.
looking at the orders now I see that ALL the BUY orders are missing.
The text was updated successfully, but these errors were encountered: