Closed davidsblom closed 1 month ago
Pasting the logs here for reference. Note that there is no intelligence in this backtest. The agent actually submits random limit orders.
One observation is that there are many InvalidStateTrigger
warnings. Then, at some point there errors appear. So, maybe it is related.
Thanks for the feedback @davidsblom
I just pushed another change which further improves and tightens the venue_order_id
indexing in the cache https://github.com/nautechsystems/nautilus_trader/commit/ee47d5ea492d3c3f8b2693b1a02f9331d095f529. Before this change, it was still possible for multiple venue order IDs to be indexed for the same client order ID.
Lets see how this goes.
Awesome! I'll give a try later this weekend.
Test is running. I'll update later tonight.
I think it is working now, at least the error hasn't happened for 2 hours. Another error occurred, but let's close this one :)
Bug Report
Expected Behavior
No errors when using the sandbox.
Actual Behavior
The execution engine throws errors when applying order filled events. The venue_order_id of the order is not consistent with the event.
Steps to Reproduce the Problem
Specifications
nautilus_trader
version: develop branch, git commit ad9a515874da677c5acd7815056dfce21b926578