开云体育

I'm not expecting anything as I can't see any other way to handle it. It's just a basic awaitio loop with tagging. Been around since the late 80's nothing particularly innovative about it. I'm just

I understand... I'm looking forward to reading the replies also.

not really, just asking for high level approach. The denizens of this forum are *usually* helpful in this regard.

Lol, I gave you my opinion... use asyncio. But you seem to expect an extremely detailed explanation of how people implement their own proprietary software. I wouldn't hold out much hope for that. You

I was one of the first users of ib_insync and I have the deepest respect for ewald.? My question is specific to the flow of the code *NOT* the environment.? I would like to know how others handle,

Clearly this question can elicit countless different responses. However, to be honest, if I had to rewrite my application from scratch... I probably would just use

That's what I expected. Seems our problems are not related.

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

Thank you.

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

Hi there I was populating an array with a list of symbols and related exchanges. I'd loop through the array and for each row call reqMktData with a new request id. This kicked off an asynch callback

I'm concerned that no one else is seeing this. Points to a failure in logic my end. I would have thought posting a bunch of reqMktData requests each with it's own unique identifier THEN handling the

Yeah, the bug I documented is only guaranteed to happen during regular trading hours too. It can be reproduced somewhat reliably with a trial account, but that code path is certainly different and the

we got the microwave because someone complained about a chocolate bar melting in their pocket.? What is REALLY strange is that if I run this script after market close it works as expected. I get all

I was just complaining. But, given how you described your script and the problem, I suppose it actually _could_ be related. When I was first investigating that issue, the initial symptom was indeed a

thanks J replied to other thread so now can say this one COMPLETE. excellent help thanks

Hi Jürgen GREAT to hear from you and happy hols to the whole Reinold clan :-) YEP another steaming pile of opportunity from TWS but I'm sure there's a reason for it. gotcha on the no client

I replied in your other topics "IO broken pipe anyone seen this recently" ( /g/twsapi/topic/io_broken_pipe_anyone_seen/95811326 ) with a procedure that might help get you decrypted

Sorry to hear you ran into one of these "ran well before now broke" issues. First of all, we have? not seen any client connection related issues. Also, there is only one socket connection between

thanks for pointing out your issue. I'm wondering if they aren't related in some way. In my case the code was working fine up until 12/16/22. Calls to historical work as expected BUT calls to