Order expiration block numbers are sometimes reported incorrectly in the client

[lampshade9909]

#The API seems to report the correctly expire date. So the problem may be with the client or whatever node/source the client gets the current block number from.

In this particular case, this number is too big, by a hundred thousand or more.

[freeatnet]

@lampshade9909 Hmm. Could you post steps to reproduce it or some logs of what the order data was?

[lampshade9909]

So I've tried reproducing it and I'm getting more confused. I can't tell it only happens sometimes, or only in some markets or what. Right now it's happening in the EOS market (for this order at least, not sure if it's order dependant) but not the PPT/OMG market, no idea why. I made a video. It's not sped up, so in this case, it ticks down by about 50 blocks in about 10 seconds. Notice the blocks aren't ticking down by 1, but instead by ~50 or so. Almost like there's some funky multiplier in there by accident. Is there any logic in the client that's doing a conversion on the expires value? If so, maybe it's converting it wrong under some circumstance.

https://www.youtube.com/watch?v=Wee_csmwfJQ