开云体育

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

Well, if you're seeing the same problem with a basic test case across different language APIs, I'd consider reaching for the usual tools like wireshark, strace to troubleshoot further. And, if the

As I said, I am asking for the forum's guidance in two regards: 1 has anyone else experienced IO issues since 12/16/22 ? 2 has the forum got any guidance as to how to resolve TCPIp type issues with

You sound pretty sure of this so I'm guessing you must've confirmed the same thing is happening when you create a simple test case using one of the ***officially*** supported API/SDKs too... yes?

this isn't a julia problem it's a TWS issue and yes I they have helped me A LOT to narrow the cause down to the IO subsystem. I'm asking if anyone else has noticed if TWS tcpip IO has been playing up

Uhhh.... this sounds like a problem w/ Jib. Have you reached out to [them](https://github.com/lbilli/Jib.jl/issues)?

Just started getting these "broken pipe" messages in code that's been working for months. Anyone know how to diagnose TWS socket issues like broken pipes. I don't even know which log to look at!!!

I looked at that before posting and the "export diagnostics" just sat there for about an hour. Is there no other way to look at the logs?

I did look at this before asking but when I ran the "export diagnostics" it just sat there for about an hour. How do you use this system please?

Hi, I have the very latest version of the API i believe... mine was working fine before yesterday.. sadly, the problem started after the auto update of TWS and the notification of availability of

Hi, is there a way to manage trades placed when TWS is closed and then reopened? I have been using reqId's to create OCA orders and then manage them whilst TWS is open. But when I close TWS and reopen

I've posted the problem to the IB support. They've known about it and asked me to upload the log. They're investigating the bug, but recommended me to install the most recent API version. Regards,

In more recent TWS versions, log decryption and export moved to Help -> Troubleshooting -> Diagnostics. Jürgen

Doing this via GUI is rather easy... select the menu option ACCOUNT, DIAGNOSTICS, then TWS Logs. It should be somewhat self explanatory from there.

Hi all never had to look at TWS logs before but now I need to. The issue is that I have NO idea how to do this. I am running a tws desktop on a linux laptop which I can access the drive on BUT I have

check below. https://stackoverflow.com/questions/45709283/i-cant-get-the-adjusted-last-from-ibapi

I am on API_Version=10.19.01... I guess that it's a TWS bug which I will have to put up with :-( [email protected]> wrote:

Hi, The same problem and just for IDEALPRO AUD.USD, other currencies are ok. But I'm using old API v971. Regards, Alexander

Is it a problem? I had to do the same thing. It's what they called that attribute.

API #163 is version 10.10.?? If you have that or more, then it sounds like an internal TWS error.