2024.03.3019:28:34.579 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:34.579 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:34.579 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:35.551 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:35.551 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:35.551 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:36.554 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:36.554 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3019:28:36.554 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
Thanks, please report if you still see the bug in post #21
2024.03.3123:09:22.659 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3123:09:22.659 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
2024.03.3123:09:22.659 iForexSessions (XAUUSD,M1) >> CTimeZoneInfo::HistoryBrokerOffset() FAILED: The requested date 2024.03.24is not found in the available history
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
fxsaber #:
Fixed in version 1.35.
Thanks for reporting this bug.
Fixed in version 1.35.
Thanks for reporting this bug.
Unfortunately, the problem is not resolved.
Unfortunately, the problem is not resolved.
MQl5 is strange!
I have already tested on 6 brokers, multiple restarts, 4 charts loaded with the indicator attached -> No errors.
I run it on PepperStone without any error on Weekend. Will update if any error while running in live account.
Thanks, please report if you still see the bug in post #21
Thanks, please report if you still see the bug in post #21
this line #149
fxsaber #:
I think you are testing the dev build that I sent you. Please use the release build on the codebase.
Update 1 April 2024 - version 1.40
Updated the 'TimeZoneInfo' library to version 1.67
Forum on trading, automated trading systems and testing trading strategies
Libraries: Local Timezones and Local Session Hours
amrali, 2024.04.01 00:17
Update 1 April 2024 - version 1.67
Fixed potential issue in the calculation of the broker GMT offset during the first hour of the trading week.
Please report if you still see the bug in post #21