No it's the same script posting the asynch requests and it has a
callback wrapper which hands back the streams from each which has
a unique identifier so I know which request is which.
I've left the script in the cron stack just to see what happens.
If nothing else it's MAKING me put in the error handling I should
have in the first place.
On 12/21/22 19:00, buddy wrote:
toggle quoted message
Show quoted text
On Wed, Dec 21, 2022 at 11:29 PM, comicpilsen wrote:
I figured that client id would cause issues in the future so
I hard coded it
into the script (ib = Jib.connect("192.168.1.219", 1234, 31))
so I always know
which script is doing what.
Last year I noticed my issue like night and day from 9.x to
10.x and rolled production back because auto-update caught me
off guard. Naturally I've stopped auto-updating. Then, out of
pure tenacity and curiosity, spent a lot of time working with IB
support to pinpoint the issue exactly (that's the reason for the
github gist).
But, I'm a little confused... are you saying that one of your
scripts makes multiple reqMktData requests yet a different
script (with different client ID) receives the tickPrices? Then
you match them up via reqId? I'm not sure that's a good idea
generally but if it works could see you hitting the same bug
that affects me - since each script would have a different
client ID.
The alternative, I think, means that you're using the async
keyword (I'm not a Julia expert) to process tickPrices via
coroutines (so, in the same thread and process) and then I'd
think you may not be hitting the bug that affects me; since it'd
all be using the same, fixed clientID in the very same process
too.
Anyway, I'm sure you looked a the github gist and can judge how
closely our issues are related. That Python code is brain-dead
simple and the explanation is as clear as can be.
It'd also be interesting if you found a different problem, even
if it was just superficially related.
