Good QA people need to have OCD and the ability to focus on a single issue for hours on end. This latest generation of workers have opposite all of that, because social media.
well, I've been having problems with the API since the change of exchange names over the weekend, but it turns out that 10.19.1f was the problem.The most recent STABLE version (10.19.1f) of TWS is buggy as hell -- pretty much unusable for me -- but as best I can tell there's no way to ROLL BACK to the prior Stable version of TWS.
well, I've been having problems with the API since the change of exchange names over the weekend, but it turns out that 10.19.1f was the problem.
There were two problems:
(i) data for continuous contracts for those instruments which had a change of exchange name wasn't working; and
(ii) the API was returning exchange name of QBALGO for an instrument instead of returning ECBOT, leading to problems with data, and generally querying TWS with the API.
An "upgrade", if you can call it that, from "Stable" 10.19.1f to "Latest" 10.20.1c seems to have fixed both problems.
KH
Why on earth don't they publish a complete errata (change log) with each version?
well, I've been having problems with the API since the change of exchange names over the weekend, but it turns out that 10.19.1f was the problem.
There were two problems:
(i) data for continuous contracts for those instruments which had a change of exchange name wasn't working; and
(ii) the API was returning exchange name of QBALGO for an instrument instead of returning ECBOT, leading to problems with data, and generally querying TWS with the API.
An "upgrade", if you can call it that, from "Stable" 10.19.1f to "Latest" 10.20.1c seems to have fixed both problems.
KH

Yup it's the API that broke as well. Specifically order submission -- I can still pull market data into Excel, but the API order submission process is completely broken. Tried the Stable, Latest, and Beta versions that were bundled with this update; doesn't work for any of them. Still works on my secondary computer that for some reason didn't auto-update like my main one did.
That's actually a Q I still don't understand: I've never used the Offline installer, to the best of my knowledge...meaning I'd assume that on a given day ALL of my TWS installations would auto-update when there's a new version...but for some reason only 1 of the 3 PC's I tried today updated. But I'm concerned they'll do so tomorrow and I'll be completely out of luck. But is there a good reason one PC's installation may update on a given day while another may not? (Maybe there are mirror download sites that get updated at different intervals? That's all I could think of.)
Did you restart that one or has it been running the whole time? I think they only check for an update when they're first executed... not while they're running.
Maybe this is your opportunity to de-compile the jar, read the obfuscated java, and cripple the original binary so it will skip the auto-update?
Or maybe you have better things to do with your time, IDK.