voyz
voyz
is this screenshot a directory on the container running IBeam? In such case the default place of inputs directory is `/srv/inputs`. You can modify it with `IBEAM_INPUTS_DIR` env var.
Well I can't figure out the setup on your end remotely, but that's what you need to figure out: how to mount the inputs correctly, as currently the `conf.yaml` doesn't...
Nice, happy to hear! 🙌 Feel free to close this issue when you're ready
If you'd like to discuss Python client libraries, I'd suggest you open a separate issue for clarity. I'd recommend using IBind
hey @gbataille thanks for reporting this. Can you give a bit more context as to when it happened? I can see that this is in the health_server, was it when...
hey @lth98 thanks for describing your issue in details 👍 My first guess would be that there are some connectivity issues between the Gateway and the IBKR: - your requests...
hey @simpzan thanks for the detailed bug report 👍 The behaviour you're observing seems in line with the filtered `/orders` endpoint (live_orders(filters=...) method) polluting the Live Order Updates WS channel....
@simpzan that's very useful. Do you also call REST /tickle endpoint apart from sending that 'tic' payload?
Right, so what seems to have worked for you is having IBeam call /tickle and have your system call that 'tic' regularly, right? That's useful to know. I've released 0.1.21rc3...
@weklund > I realize I haven't been as active addressing open issues for IBind Honestly, don't feel bad. You did superb job leading the PR front with the CI, contributing,...