-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
fix: process pending order update for active order book #1060
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,6 +62,33 @@ func BatchRetryPlaceOrder(ctx context.Context, exchange types.Exchange, errIdx [ | |
return createdOrders, err | ||
} | ||
|
||
// BatchPlaceOrderChan post orders with a channel, the created order will be sent to this channel immediately, so that | ||
// the caller can add the created order to the active order book or the order store to collect trades. | ||
// this method is used when you have large amount of orders to be sent and most of the orders might be filled as taker order. | ||
// channel orderC will be closed when all the submit orders are submitted. | ||
func BatchPlaceOrderChan(ctx context.Context, exchange types.Exchange, orderC chan types.Order, submitOrders ...types.SubmitOrder) (types.OrderSlice, []int, error) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is unrelated, but we might need this in the future |
||
defer close(orderC) | ||
|
||
var createdOrders types.OrderSlice | ||
var err error | ||
var errIndexes []int | ||
for i, submitOrder := range submitOrders { | ||
createdOrder, err2 := exchange.SubmitOrder(ctx, submitOrder) | ||
if err2 != nil { | ||
err = multierr.Append(err, err2) | ||
errIndexes = append(errIndexes, i) | ||
} else if createdOrder != nil { | ||
createdOrder.Tag = submitOrder.Tag | ||
|
||
orderC <- *createdOrder | ||
|
||
createdOrders = append(createdOrders, *createdOrder) | ||
} | ||
} | ||
|
||
return createdOrders, errIndexes, err | ||
} | ||
|
||
// BatchPlaceOrder | ||
func BatchPlaceOrder(ctx context.Context, exchange types.Exchange, submitOrders ...types.SubmitOrder) (types.OrderSlice, []int, error) { | ||
var createdOrders types.OrderSlice | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a rare condition that a pending order and a new coming order are updated at the same timestamp (in millisecond or even in second).
Another way is to compare the filled amount or the state change.