You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It happened not because of a bug in the logic caused the data to get in such a state where it was possible to happen, but rather, because a manual MySQL query was incorrectly ran against the database which caused the record to be in status it wasn't supposed to be in (SELL_FILLED when it was supposed to be BUY_FILLED).
This use of stdClass as the result of a json_decode() on the meta column of trade_repeater is an area that highly could use some refactoring. Making use of class objects, interfaces, etc. So any 'fixing' on this exact issue while it is in this state would have to come also with the acceptance that it will be probably thrown away in that refactoring.
Still, logging an issue here for tracking purposes:
This one is a bit of a mixed bag....
status
it wasn't supposed to be in (SELL_FILLED
when it was supposed to beBUY_FILLED
).stdClass
as the result of ajson_decode()
on themeta
column oftrade_repeater
is an area that highly could use some refactoring. Making use of class objects, interfaces, etc. So any 'fixing' on this exact issue while it is in this state would have to come also with the acceptance that it will be probably thrown away in that refactoring.Still, logging an issue here for tracking purposes:
The text was updated successfully, but these errors were encountered: