From 1ba92a026f167d5f75d168b56ffaae8e204aa0b1 Mon Sep 17 00:00:00 2001 From: Tyler Goodlet Date: Thu, 1 Dec 2022 15:49:38 -0500 Subject: [PATCH] TOSQUASH: 552a8c298cd (return index for arrow..) --- piker/ui/order_mode.py | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/piker/ui/order_mode.py b/piker/ui/order_mode.py index fdd2d188..1dd49872 100644 --- a/piker/ui/order_mode.py +++ b/piker/ui/order_mode.py @@ -1037,10 +1037,11 @@ async def process_trade_msg( # should only be one "fill" for an alert # add a triangle and remove the level line req = Order(**req) + index = flume.get_index(time.time()) mode.on_fill( oid, price=req.price, - arrow_index=flume.get_index(time.time()), + arrow_index=index, ) mode.lines.remove_line(uuid=oid) msg.req = req @@ -1068,26 +1069,27 @@ async def process_trade_msg( action = order.action details = msg.brokerd_msg + # TODO: put the actual exchange timestamp? + # NOTE: currently the ``kraken`` openOrders sub + # doesn't deliver their engine timestamp as part of + # it's schema, so this value is **not** from them + # (see our backend code). We should probably either + # include all provider-engine timestamps in the + # summary 'closed' status msg and/or figure out + # a way to indicate what is a `brokerd` stamp versus + # a true backend one? This will require finagling + # with how each backend tracks/summarizes time + # stamps for the downstream API. + index = flume.get_index( + details['broker_time'] + ) + # TODO: some kinda progress system mode.on_fill( oid, price=details['price'], + arrow_index=index, pointing='up' if action == 'buy' else 'down', - - # TODO: put the actual exchange timestamp - arrow_index=flume.get_index( - # TODO: note currently the ``kraken`` openOrders sub - # doesn't deliver their engine timestamp as part of - # it's schema, so this value is **not** from them - # (see our backend code). We should probably either - # include all provider-engine timestamps in the - # summary 'closed' status msg and/or figure out - # a way to indicate what is a `brokerd` stamp versus - # a true backend one? This will require finagling - # with how each backend tracks/summarizes time - # stamps for the downstream API. - details['broker_time'] - ), ) # TODO: append these fill events to the position's clear