The bug is stable, reproduces each time the app attempting to use the IB connector. I'm using the latest version of the IB connector, but the bug was also present on the previous version too.
Steps to repro:
1. disable all data sources except for IB
2. run any strategy that uses SPY
I can't copy the text to the clipboard, as the button (and whole UI) is freezed. After 5-10 seconds the app closes itself.
Tws settings:
Steps to repro:
1. disable all data sources except for IB
2. run any strategy that uses SPY
I can't copy the text to the clipboard, as the button (and whole UI) is freezed. After 5-10 seconds the app closes itself.
Tws settings:
Rename
I have two more bugs found (although minor ones), so I believe each one should be described in a separate thread, right?
Please try this as a solution:
Exception "Input string was not in a correct format" in IB provider (Solved)
Sure.
Exception "Input string was not in a correct format" in IB provider (Solved)
QUOTE:
I have two more bugs found (although minor ones), so I believe each one should be described in a separate thread, right?
Sure.
No need to make you dig so hard for this IB API bug:
Solution:
Set up Windows to use a printable character as the thousands grouping separator. It might have to be a comma or a period.
Solution:
Set up Windows to use a printable character as the thousands grouping separator. It might have to be a comma or a period.
And note, this is a bug in TWS not WL. So you could report it to IB and I’m sure they’ll fix it in their next release. 😅
Yes, we've all done that about 2 years ago.
They haven't reported in the release notes that this has changed, but it's probably time for us to update the API anyway.
They haven't reported in the release notes that this has changed, but it's probably time for us to update the API anyway.
I think I see how to work around this.
Can you confirm that you're using one of these CutureInfos?
To do it, just open a new C# Coded strategy and paste this line in the Initialize() section -
Run Strategy.
Does the result from the Debug Log match one of the above?
If it doesn't match, did you remember if you changed the thousands grouping manually to whitespaces?
Can you confirm that you're using one of these CutureInfos?
CODE:
dje-NE Zarma (Niger) khq-ML Koyra Chiini (Mali) mfe-MU Morisyen (Mauritius) nso-ZA Sesotho sa Leboa (South Africa) ses-ML Koyraboro Senni (Mali) tn-BW Setswana (Botswana) tn-ZA Setswana (South Africa) twq-NE Tasawaq (Niger) xh-ZA isiXhosa (South Africa)
To do it, just open a new C# Coded strategy and paste this line in the Initialize() section -
CODE:
WriteToDebugLog(System.Globalization.CultureInfo.CurrentCulture);
Run Strategy.
Does the result from the Debug Log match one of the above?
If it doesn't match, did you remember if you changed the thousands grouping manually to whitespaces?
Well, I have an English version of Windows, with Ru culture, so the output is:
---Symbol by Symbol Debug Logs---
---Si---
ru-RU
I didn't change any regional settings (e.g., whitespaces) myself.
Thank you for the answer. I realize that it's a bug in TWS. But, it seems to be strange that WL crashes on this, as some changes in strategies may not be saved. A handler to avoid crash would be really appreciated.
---Symbol by Symbol Debug Logs---
---Si---
ru-RU
I didn't change any regional settings (e.g., whitespaces) myself.
Thank you for the answer. I realize that it's a bug in TWS. But, it seems to be strange that WL crashes on this, as some changes in strategies may not be saved. A handler to avoid crash would be really appreciated.
Did you see the solution in Post #3?
One way or another, you must be using a whitespace for thousands grouping. You'll have to change that.
One way or another, you must be using a whitespace for thousands grouping. You'll have to change that.
Your Response
Post
Edit Post
Login is required