Mv to ib_async.. finally. #68

New Issue

goodboy · 2026-01-26T16:15:39Z

goodboy commented

2026-01-26 16:15:39 +00:00

Already had a GH ish reported,

https://github.com/pikers/piker/issues/539

i was only putting it off out of laziness and/or non-necessity BP

BUT we actually have a reason now to switch!

Solved by #77.

“Fixes” we-needed that #77 added,

(Prolly shoulda wrote them there first.. which is done now)

(fe207a69) move to aeventkit from the same forked lib set.
(f78362b2) the IB.qualifyContractsAsync() method now offers a returnAll: bool which solves an issue i’ve seen with various so called “ambiguous” contract queries,
https://github.com/ib-api-reloaded/ib_async/blob/main/ib_async/ib.py#L2115

For ex., currently we can’t load silver futes contracts due to the old ib_insync only warning on such cases..
```
Jan 26 11:21:49 (brokerd.ib[6272cb], 284364, no task context))
[WARNING] piker.ib_insync ib.py:1806 Ambiguous contract:
Future(symbol='si', lastTradeDateOrContractMonth='20261229',
exchange='COMEX'), possibles are [Contract(secType='FUT',
conId=535526329, symbol='SI',
lastTradeDateOrContractMonth='20261229', multiplier='5000',
exchange='COMEX', currency='USD', localSymbol='SIZ6',
tradingClass='SI'), Contract(secType='FUT', conId=842178357,
symbol='SI', lastTradeDateOrContractMonth='20261229',
multiplier='1000', exchange='COMEX', currency='USD',
localSymbol='SILZ6', tradingClass='SIL')]
```
^ which occurs just before a crash originating in our piker.brokers.ib.api.Client.get_sym_details() which fails to find a single matching contract based on the fqme requested from the the chart’s mkt search..
- (6834dd4c) started expecting a cons: list[Contract].
- (f78362b2) specifically is tested to handle futes contracts!
there’s an outstanding symbol search issue (which i discovered was still there when we were on ib_insync that i’ve deferred to,
- https://www.pikers.dev/pikers/piker/issues/85
- (31bf5f55) adds better server-side logging for tracing the results for the search query, though we need to do this inside .ib.api.Client meths next to figure out wtf is up..

Additional improvements,

see #77.

Already had a GH ish reported, https://github.com/pikers/piker/issues/539 i was only putting it off out of laziness and/or non-necessity BP BUT we actually have a reason now to switch! Solved by #77. --- #### "Fixes" we-needed that #77 added, (Prolly shoulda wrote them there first.. which is done now) - [x] (fe207a69) move to `aeventkit` from the same forked lib set. - [x] (f78362b2) the `IB.qualifyContractsAsync()` method now offers a `returnAll: bool` which solves an issue i've seen with various so called "ambiguous" contract queries, https://github.com/ib-api-reloaded/ib_async/blob/main/ib_async/ib.py#L2115 For ex., currently we can't load silver futes contracts due to the old `ib_insync` only warning on such cases.. ```python Jan 26 11:21:49 (brokerd.ib[6272cb], 284364, no task context)) [WARNING] piker.ib_insync ib.py:1806 Ambiguous contract: Future(symbol='si', lastTradeDateOrContractMonth='20261229', exchange='COMEX'), possibles are [Contract(secType='FUT', conId=535526329, symbol='SI', lastTradeDateOrContractMonth='20261229', multiplier='5000', exchange='COMEX', currency='USD', localSymbol='SIZ6', tradingClass='SI'), Contract(secType='FUT', conId=842178357, symbol='SI', lastTradeDateOrContractMonth='20261229', multiplier='1000', exchange='COMEX', currency='USD', localSymbol='SILZ6', tradingClass='SIL')] ``` ^ which occurs just before a crash originating in our `piker.brokers.ib.api.Client.get_sym_details()` which fails to find a *single* matching contract based on the fqme requested from the the chart's mkt search.. * (6834dd4c) started expecting a `cons: list[Contract]`. * (f78362b2) specifically is tested to handle futes contracts! - [x] there's an outstanding symbol search issue (which i discovered was still there when we were on `ib_insync` that i've deferred to, * https://www.pikers.dev/pikers/piker/issues/85 * (31bf5f55) adds better server-side logging for tracing the results for the search query, though we need to do this inside `.ib.api.Client` meths next to figure out wtf is up.. --- ### Additional improvements, see #77.

2026-03-05T15:39:02,475893250-05:00.png

53 KiB