Closed mehtadone closed 6 years ago
This problem may be related to something culture related where the decimal separator is a comma which may cause ExchangeSharp to not be able to accurately create a request?
Maybe. This is running on Azure functions and I can't seem to find a culture setting. I'll keep digging and if I figure it out, will update on here for future reference.
I think there is something wrong in the ExchangeSharp library. I updated to the latest version and forced culture in code to US. I get another error on GetOrder, with a similar error message. I logged the orderid just before the error:
2018-05-28T10:44:55.144 [Info] 2018-05-28 10:44:55.144 +00:00 [Information] GetOrder(13561326, CMTBTC)
2018-05-28T10:44:55.220 [Info] 2018-05-28 10:44:55.220 +00:00 [Information] CancelOrder(13561326, CMTBTC)
2018-05-28T10:44:55.470 [Error] 2018-05-28 10:44:55.299 +00:00 [Error] Error on BuyTimer
ExchangeSharp.APIException: {"code":-1100,"msg":"Illegal characters found in parameter 'orderId'; legal range is '^[0-9]{1,20}$'."}
at ExchangeSharp.APIRequestMaker.<MakeRequestAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
You can see the orderID is valid, but it feels like the library may be converted to scientific notation.
Think this is all related to exchangesharp. Closing on here as its not really Mynt issue per say
I'm getting this exception thrown when an order is about to be placed. Any thoughts? I am assuming user error but my AmountToInvestPerTrader is 0.02