Second day is always missed in logs - why?

[vritme]

Is it just logging imperfection or second day of each month/year/any dataset is always missing in the resulting dataset? @ffeast

[vritme]

[vritme]

[ffeast]

Hi
Need to look into it. Have you checked the actual data in the resulting files? Are any bars missing?

[vritme]

I see lot's of yearly downloaded files starting from 3-rd of January, but that's may be because of moex work time.

Also i've made some half of the years downloads like BR from 2019.07.01 to 2019.12.31 and in this case there IS 07.02 date, as well as 07.01 and 07.03. So it looks quite indefinite and confusing..

Still, if we look at logs, it tolds us, that query with day 2 is always missed for no reason. I think it should be more accurate in logging anyway..

[vritme]

So have you discovered something about it?

[vritme]

Did some more research.
The app in fact missed second day of requested period, which in reality has quotes.
So you can see it on February, but on the next month, March, second day was downloaded successfully. So it looks like unstable behaviour around 2-nd day of period.
Maybe it's only with ticks, but looks like it's some general bug.

[vritme]

I checked all months of 2016 with working days on 2-nd day of month. Only February has problem, but still, very inconvenient to checks manually gigabytes of txt's...

[ffeast]

Confirm, there's a bug. Thanks for you report. The cause is slightly different from what you described but it still needs to be fixed

[ffeast]

Should be fixed in 4.0.2

[ffeast]

Solved long ago, closing