Matt Stancliff
Matt Stancliff
> But ib_async only fetches 1 open order which is the stop, the profit taker is missing. That does sound odd. Seems it should show either all or nothing, but...
Also make sure you have error handlers attached to all the important points like shown below because it's possible for child orders to have errors and fail to be placed...
> compiled as go program(s) what? that's probably even worse. > instead of tcl scripts. over time that would be nice, but the more I look at the state of...
Yes, exactly all those parts. > the code is so highly optimized that it is difficult to write isolated tests for many of the functions. I seem to recall many...
We should really provide a better training workflow for onboarding people into the ecosystem here since these problems are the most common confusion around usage. `ib_async` is _best_ used in...
> the method declaration says async, and I see it returns an awaitable (future), but it's not defined as async, i.e. not: `async def reqAccountSummaryAsync(self)`. This is actually perfectly valid...
> wait for the end signal before accessing the obj. That's an important part to understand too! When requesting account data (or _any_ data with the IBKR APIs) _every field_...
If you truly want One System to Rule them All, just learn clickhouse and be at peace forever. Clickhouse has turned into basically what I wish redis would have been...
Yeah, it's one of those "would be fun/neat/interesting" ideas to have and technically fun to build over time, but it's worth considering if other projects already do this better and...
That's actually normal because each field is populated asynchronously, so sometimes it takes a couple seconds for all data to "appear" after being requested. You could either wait longer before...