Page 3 of 3

Re: Zkb fetch error

Posted: Tue May 21, 2019 19:40
by anchorhead
Hi, i have discover a new bug i think.

Salvoxia, your fix is ok for me also but on my kb there was a kill who didn't want fetched. 0 kills posted 0 skipped ...

I didn't understand why ... all settings are ok for me, no error appear after fetch

In zkb fetch setings i have 4 fetch api url entered.

I tried to uncheck 3/4 api url for see. And 2 surprise :

kill was posted and uncheck do nothing even if i did a SAVE click, case back checked again

Re: Zkb fetch error

Posted: Tue May 21, 2019 19:46
by Salvoxia
Hi,

could you provide me with your fetch URL, timestamp and the kill in question?

Unticking the "fetch" checkboxes for different URLs is not saved. This setting is just applied for one manually triggered cycle. That's working as intended ;)

Best Regards,
Salvoxia

Re: Zkb fetch error

Posted: Tue May 21, 2019 20:01
by anchorhead
After tried again to fetch kill :
2019-05-18 15:00:00 : works
2019-05-10 15:00:00 : not works

2019-05-10 is before kill, kb should fetch kill no ?

Re: Zkb fetch error

Posted: Wed May 22, 2019 15:41
by Salvoxia
Maybe there's a misunderstanding as to how the fix (or the zKB API now) works.
The kill in question has the timestamp 2019-05-18 21:10.
The zKB API now forces you to specify a start time AND an end time, while the difference between start and end must not be more than one day.
So if you start fetching with a last kill timestamp of 2019-05-10 15:00:00, only kills between 2019-05-10 15:00:00 and 2019-05-11 15:00:00 will be fetched.
The next cycle will fetch all kills between 2019-05-11 15:00:00 and 2019-05-12 15:00:00 and so on and so forth.
So you'd have to fetch 9 times to get the kill from 2019-05-18 21:10 when starting at 2019-05-10 15:00:00. After eight times your last kill timestamp will be at 2019-05-18 15:00:00, so fetching one more time will move the fetching window so that the kill is inside it.
(This example assumes a negative time offset of 0 hours and that there are no kills between the start timestamp and the kill in question.)

With this in mind, what you described sounds like "working as intended".

Did this explanation help you?

Best Regards,
Salvoxia

Re: Zkb fetch error

Posted: Wed May 22, 2019 19:23
by anchorhead
In that case i understand.

For a new kb, with lot of kills, there are lot of fetched needed for have all kills, right ?

Thanks You for your explanation :)

Re: Zkb fetch error

Posted: Thu May 23, 2019 03:00
by raykai
my cron from /evekb/cron/cron_zkb.php is giving me errors :

[WARNING] Endpoint https://esi.evetech.net/v2/universe/names/ warning: 299 - This route is deprecated
[WARNING] Endpoint https://esi.evetech.net/v2/universe/names/ warning: 299 - This route is deprecated
/common/includes/class.dbnormalquery.php on line 46

Re: Zkb fetch error

Posted: Thu May 23, 2019 12:51
by Salvoxia
Hi,

I'm aware of the warnings, but they are only warnings and will not prevent kills from being posted.
The last line however is a problem, but there must be more, something like "Database error: ...". Without that, I cannot analyze the problem.
Could please provide the remainder of the message?

Best Regards,
Salvoxia