Comparing 4cb240adbe..db34999553 - piker - Pikers Dev

..

Author	SHA1	Message	Date
Tyler Goodlet	db34999553	Bump `brokers.toml`, update ib and deribit sections For `[ib]` adjust content to match changes to the `dockering/ib/README.rst` and for `[deribit]` toss in the WIP options related params for anyone who wants to play around with @nt's work.	2026-01-06 23:44:33 -05:00
Tyler Goodlet	a63c7b13e2	Bump ib-container docs and compose file Add necessary details for the `brokers.toml`, cleanup and link to the new GH container repo in the `docker-compose.yml`.	2026-01-06 23:44:33 -05:00
Tyler Goodlet	3b18233573	Bump various `.brokers.core` doc string content/style	2026-01-06 23:44:33 -05:00
Tyler Goodlet	b525fa35fe	ib: multiline stylings, typing, timeout report	2026-01-06 23:44:33 -05:00
Tyler Goodlet	731166072d	Woops, fix to read `.api_port` ref from the `Client.ib.client`..	2026-01-06 23:44:33 -05:00
Tyler Goodlet	4cdef4d101	Support per-`ib.vnc_addrs` vnc passwords Such that the `brokers.toml` can contain any of the following <port> = dict\|tuple styles, ```toml [ib.vnc_addrs] 4002 = {host = 'localhost', port = 5900, pw = 'doggy'} # host, port, pw 4002 = {host = 'localhost', port = 5900} # host, port, pw 4002 = ['localhost', 5900] # host, port, pw ``` With the first line demonstrating a vnc-server password (as normally set via a `.env` file in the `dockering/ib/` subdir) with the `pw =` field. This obviously removes the hardcoded `'doggy'` password from prior. Impl details in `.brokers.ib._util`: - pass the `ib.api.Client` down into `vnc_click_hack()` doing all config reading within and removing host, port unpacking in the callingn `data_reset_hack()`. - also pass the client `try_xdo_manual()` and comment (with plans to remove) the recently added localhost-only fallback section since we now have a fully working py vnc client again with `pyvnc` B) - in `vnc_click_hack()` match for all the possible config line styles and, * pass any `pw` field to `pyvncVNCConfig`, * continue matching host, port without password, * fallthrough to raising a val-err when neither ^ match.	2026-01-06 23:44:33 -05:00
Tyler Goodlet	fd725743a1	ib: bump `docker/ib/README.rst` For the new github image, a high-level look at its basic features/usage/docs and prosing around our expected default usage with the `piker.brokers.ib` backend.	2026-01-06 23:44:33 -05:00
Tyler Goodlet	64ebfd226f	ib.feed: better no-bars error-log message format	2026-01-06 23:44:33 -05:00
Tyler Goodlet	e20aa4a2a6	Set `.bs_mktid` on all IB position-msg emissions..	2026-01-06 23:44:33 -05:00
Tyler Goodlet	007e7e343b	Switch to `pyvnc` for IB reset hackz It actually works for vncAuth(2) (thank god!) which the previous `asyncvnc` did not, and seems to be mostly based on the work from the `asyncvnc` author anyway (so all my past efforts don't seem to have been in vain XD). NOTE, the below deats ended up being factored in earlier into the `pyproject.toml` alongside nix(os) support needed for testing and landing this history. As the such, the comments are the originals but the changes are not. Deats, - switch to `pyvnc` async API (using `asyncio` again obvi) in `.ib._util._vnc_click_hack()`. - add `pyvnc` as src installed dep from GH. - drop `asyncvnc` as dep. Other, - update `pytest` version range to avoid weird auto-load plugin exposed by `xonsh`? - add a `tool.pytest.ini_options` to project file with vars to, - disable that^ `xonsh` plug using `addopts = '-p no:xonsh'`. - set a `testpaths` to avoid running anything but that subdir. - try out the `'progress'` style console output (does it work?).	2026-01-06 23:44:33 -05:00
Tyler Goodlet	0817b2ab4b	Convert remaining `.to_asyncio.open_channel_from()` to `chan` fn-sig usage	2026-01-06 23:44:33 -05:00
Tyler Goodlet	43e505e88f	`ib.feed`: finally solve `push()` exc propagation Such that if/when the `push()` ticker callback (closure) errors internally, we actually eventually bubble the error out-and-up from the `asyncio.Task` and from there out the `.to_asyncio.open_channel_from()` to the parent `trio.Task`.. It ended up being much more subtle to solve then i would have liked thanks to, - whatever `Ticker.updateEvent.connect()` does behind the scenes in terms of (clearly) swallowing with only log reporting any exc raised in the registered callback (in our case `push()`), - `asyncio.Task.set_excepion()` never working and instead needing to resort to `Task.cancel()`, catching `CancelledError` and re-raising the stashed `maybe_exc` from `push()` when set.. Further this ports `.to_asyncio.open_channel_from()` usage to use the new `chan: tractor.to_asyncio.LinkedTaskChannel` fn-sig API, namely for `_setup_quote_stream()` task. Requires the latest `tractor` updates to the inter-eventloop-chan iface providing a `.set_nowait()` and `.get()` for the `asyncio`-side. Impl deats within `_setup_quote_stream()`, - implement `push()` error-bubbling by adding a `maybe_exc` which can be set by that callback itself or by its registering task; when set it is both, * reported on by the `teardown()` cb, * re-raised by the terminated (via `.cancel()`) `asyncio.Task` after woken from its sleep, aka "cancelled" (since that's apparently one of the only options.. see big rant further todo comments). - add explicit error-tolerance-tuning via a `handler_tries: int` counter and `tries_before_raise: int` limit such that we only bubble a `push()` raised exc once enough tries have consecutively failed. - as mentioned, use the new `chan` fn-sig support and thus the new method API for `asyncio` -> `trio` comms. - a big TODO XXX around the need to use a better sys for terminating `asyncio.Task`s whether it's by delegating to some `.to_asyncio` internals after a factor-out OR by potentially going full bore `anyio` throughout `.to_asyncio`'s impl in general.. - mk `teardown()` use appropriate `log.<level>()`s based on outcome. Surroundingly, - add a ton of doc-strings to mod fns previously missing them. - improved / added-new comments to `wait_on_data_reset()` internals and anything changed per ^above. NOTE, resolved conflicts on `piker/brokers/ib/feed.py` due to `brokers_refinery` commit: `d809c797` `.brokers.ib.feed`: better `tractor.to_asyncio` typing and var naming throughout!	2026-01-06 23:44:33 -05:00
Tyler Goodlet	b31ca5c3c6	`ib`: various type-annot, multiline styling and todos updates	2026-01-06 23:44:33 -05:00
Tyler Goodlet	5342f163fb	ib: add venue-hours checking Such that we can avoid other (pretty unreliable) "alternative" checks to determine whether a real-time quote should be waited on or (when venue is closed) we should just signal that historical backfilling can commence immediately. This has been a todo for a very long time and it turned out to be much easier to accomplish than anticipated.. Deats, - add a new `is_current_time_in_range()` dt range checker to predicate whether an input range contains `datetime.now(start_dt.tzinfo)`. - in `.ib.feed.stream_quotes()` add a `venue_is_open: bool` which uses all of the new ^^ to determine whether to branch for the short-circuit-and-do-history-now-case or the std real-time-quotes should-be-awaited-since-venue-is-open, case; drop all the old hacks trying to workaround not figuring that venue state stuff.. Other, - also add a gpt5 composed parser to `._util` for the `ib_insync.ContractDetails.tradingHours: str` for before i realized there was a `.tradingSessions` property XD - in `.ib_feed`, * add various EG-collapsings per recent tractor/trio updates. * better logging / exc-handling around ticker quote pushes. * stop clearing `Ticker.ticks` each quote iteration; not sure if this is needed/correct tho? * add masked `Ticker.ticks` poll loop that logs. - fix some `str.format()` usage in `._util.try_xdo_manual()` NOTE, resolved conflicts on `piker/brokers/ib/feed.py` due to rebasing onto up stream `brokers_refinery` commit, `d809c797` `.brokers.ib.feed`: better `tractor.to_asyncio` typing and var naming throughout	2026-01-06 23:44:33 -05:00
Tyler Goodlet	09059ce956	ib: never relay "Warning:" errors to EMS.. You'd think they could be bothered to make either a "log" or "warning" msg type instead of a `type='error'`.. but alas, this attempts to detect all such "warning"-errors and never proxy them to the clearing engine thus avoiding the cancellation of any associated (by `reqid`) pre-existing orders (control dialogs). Also update all surrounding log messages to a more multiline style.	2026-01-06 23:44:33 -05:00
Tyler Goodlet	8283a1d482	ib: jig `.data_reset_hack()` with vnc-client failover Since apparently porting to the new docker container enforces using a vnc password and `asyncvnc` seems to have a bug/mis-config whenever i've tried a pw over a wg tunnel..? Soo, this tries out the old `i3ipc`-win-focus + `xdo` click hack when the above fails. Deats, - add a mod-level `try_xdo_manual()` to wrap calling `i3ipc_xdotool_manual_click_hack()` with an oserr handler, ensure we don't bother trying if `i3ipc` import fails beforehand tho. - call ^ from both the orig case block and the failover from the vnc-client case. - factor the `+no_setup_msg: str` out to mod level and expect it to be `.format()`-ed. - refresh todo around `asyncvnc` pw ish.. - add a new `i3ipc_fin_wins_titled()` window-title scanner which predicates input `titles` and delivers any matches alongside the orig focused win at call time. - tweak `i3ipc_xdotool_manual_click_hack()` to call ^ and remove prior unfactored window scanning logic.	2026-01-06 23:44:33 -05:00

Diff Content Not Available