EDK 4.4.3.0 (July 2019 1.0)

[underwoodr]

You still have this problem? I can't reproduce it...

Hi,
I got around it by changing the timestamp offset from 2 -> 1, and then updating the feeds one at a time, once they reached the end, they stayed at current date as intended.
Not sure what the actual problem was, but it is no longer there

[Ishmahel_Eve]

Hello Everyone, i have this issue while installing brand new version from scrap

Install Step 5 / 8

Fatal error: Uncaught exception 'Swagger\Client\ApiException' with message 'API call to https://esi.evetech.net/v2/search/?cate ... e&strict=1 failed: Received HTTP code 403 from proxy after CONNECT' in /membri/logisticawhlive/common/esi/lib/ApiClient.php:258 Stack trace: #0 /membri/logisticawhlive/common/esi/lib/EsiClient/SearchApi.php(404): Swagger\Client\ApiClient->callApi('/v2/search/', 'GET', Array, '', Array, '\\Swagger\\Client...', '/v2/search/') #1 /membri/logisticawhlive/common/esi/lib/EsiClient/SearchApi.php(307): EsiClient\SearchApi->getSearchWithHttpInfo(Array, 'Insurgent New E...', NULL, NULL, NULL, NULL, true) #2 /membri/logisticawhlive/install/install_step5.php(221): EsiClient\SearchApi->getSearch(Array, 'Insurgent New E...', NULL, NULL, NULL, NULL, true) #3 /membri/logisticawhlive/install/install_step5.php(253): Api->getExternalIdForEntity('Insurgent New E...', 'corporation') #4 /membri/logisticawhlive/install/install_step5.php(131): Api->getCorporationId('Insurg in /membri/logisticawhlive/common/esi/lib/ApiClient.php on line 258

[MrJayIsAGoon]

Any hope of at least getting a database update?

[NoRiddle]

Any hope of at least getting a database update?

Well, i second that too...
Would be really nice with an update...

[WillusKillus]

Unfortunately as /startTime & /endTime/ have been deprecated by zkill, it is no longer possible to fetch kills this way.

I believe using ESI is also no longer possible due to the recent changes.

EDIT: It's still possible to get zKB fetch working using delakut's helpful fixes from their post.

I get an strange issue where it stops filling kills on the 31st of January every year. When this happens I just make sure it's pulled in everything then change the date to the 1st of February and it continues fine.

EDIT2: Noticed another issue when adding historical kills to a new board. When the amount of kills in a month is more than the limit set in "max number of kills to process per run" it will find kills up to that amount, then skip to the next month. So if you had 1000 kills in March 2014, it would find 100 and skip 900. Manually resetting the date will pull another 100 so it's necessary to keep manually going back to get all the kills.

[MrJayIsAGoon]

May this project forever rest in peace.

I for one am incredibly thankful for the thousands of killmails that passed through this platform. It shall be missed.