Data gap issue

Hi,

It took some time, more than a year to understand the problem I've facing.
My post includes some analysis of QC data against broker (oanda) data with timezone handlings. 
 

First of all some background information about the broker API:

OANDA API uses dates in RFC3339 or unix time representation. Here is a sample request/response:

Then, some here is my understanding about lean datetime handling:

• The SetTimeZone can set used to time zone, but default time is set to New York timezone.
• QCAlgorithm.Time has not "timezone markup", but it represents the algorithm timezone. This "markup" is important to convert the Time to other timezones. That means that functions such as ToUniversalTime() does not work because it lacks this "markup".
• Nevertheless Lean provide a means to to get the UTC time: QCAlgorithm.UtcTime
• The timestamp of the data uses the Exchange.TimeZone, so to convert into UTC we must use
• data[symbol].Time.ConvertToUtc(Portfolio.Securities[symbol].Exchange.TimeZone)

Question, will the machine timezone influence the algorithm? (I dont think so, but for the moment I have no evidence)

Now the problem I've encountered is related to data not being fed into the algorithm on sundays.

Note however, that data prices are exactly the same as the broker prices when the data is fed. The only issue I encounter is the lack of data on sundays.

Here is how to reproduce:

Use EUR_USD instrument and start algo on sunday.

For instance, the EURUSD market hours starts on the 7 april 17:00 Exchange Time or 21:00 UTC time. In the below logs you can see that the data provided by QC starts from 23:OO UTC time, and not from 21:00 as expected.

Please find below the logs of the data for the algo Run between 2019-04-07 => 2019-04-08
 

Here, you can see prices the broker provides data since the market openning.

Please refer to the below backtest.