ib_2025_updates: to make it not suck despite edwault's epic exit #59
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "ib_2025_updates"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Mostly fixes from having not run this backend for a while (over the summer of 2025) when a bit of my infra “died” and I had to re-hack various deps, error handling, and order ctl jigging after #44, #45 and #52.
Summary of “improvements”
stopped relaying “warning” API errors-msgs through the EMS since most are benign and shouldn’t cause order-entry-session-cancellation (which can leave actual stale live orders with ib’s EMS and
piker.clearingthinking they’re rejected/cancelled).5342f16 adds legit venue “hours checking”,
type-annots and code styling modernizations.
43e505e8 solves an inter-API-connector issue with solving
asyncio-sidepush()exc propagation,porting to modern
tractor.to_asyncioAPI updates, namely:007e7e3 switches to the new VNC client lib,
pyvnc, sinceasyncvncappears to be un-maintained and i already could never get the password submission to work with our container, the new version of which enforces it,try_xdo_manual()to work around this in 8283a1d4.ib.vnc_addrsvnc passwords in thebrokers.tomlconfig.Set.bs_mktidon all IB position-msg emissions so that order-tracking in.ui.order_modenever is erroneous..BrokerPositionfirst!Bump
docker/ib/README.rstafter moving to the new GH project/image.brokers.toml.rando
.brokers.coredoc str updates.1674f99214todb34999553db34999553to4cb240adbe4cb240adbeto55116eea01