-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notice on ship drop data storage and dumping #37
Comments
Got it. |
Exciting stuff. Thanks for the ping! |
Ping @Gizeta @Acrone, the server url is updated to http://poidb.0u0.moe/. The old http://citrus.dazzyd.org may be unusable someday. |
@yukixz There are few issues with the site / dumps that just pop up recently.
$ curl -vIk https://poi.io 2>&1 | grep 'expire date'
* expire date: Sep 15 02:53:34 2019 GMT
$ curl -vIk https://poi.0u0.moe 2>&1 | grep 'expire date'
* expire date: Sep 15 02:53:34 2019 GMT
# just in case, not expired yet
$ curl -vIk https://poidb.0u0.moe 2>&1 | grep 'expire date'
* expire date: Oct 4 02:06:07 2019 GMT
|
@gakada so terrible...
|
@KagamiChan can it be due to poooi/poi@dd8ab77? Right now plugin-report is sending data via |
Thanks for catching this issue It turns out that I'll update the reporter plugin to use https instead |
@gakada The new plugin is live, could you please help monitor 1 or 2 days later? |
Yeah, I will check if % goes back up in next few dumps. |
@gakada Thanks, I've confirmed that we have data from newer version of poi |
It is back to normal mostly, 2-3x more reports from poi and 2x for the percentage. |
@yukixz having problems with the current dump for the last few days: tmp $ curl -sI https://poi.moe/dump/dropshiprecords.gz | grep content-length
content-length: 128815104
tmp $ wc -c dropshiprecords.gz
128815104 dropshiprecords.gz
tmp $ sha1sum dropshiprecords.gz
a6c6b569f9e287340e2293a2db3868653c7f6765 dropshiprecords.gz
tmp $ gunzip dropshiprecords.gz
gzip: dropshiprecords.gz: unexpected end of file |
@gakada Dumping again now. |
Thanks, now it is fine. |
@yukixz It looks like current dumps are just giving home page HTML. For example, https://poi.moe/dump/passeventrecords.gz just shows the poi home page. Happens both in browser and with curl. |
Hi @Tibowl please try https://api.poi.moe/dump/passeventrecords.gz we've made a separation for website and api server, I thought the change has been announced but seems not yet. sorry for that Btw, it is a known issue that due to network incompatibility, we have less reports since last December |
I added some question marks in https://github.com/poooi/poi-server/wiki as those seem to be enabled, but I don't know what are the links to their current dumps (two of them have monthly archived dumps). |
Thanks @gakada We disabled file listing for security reasons, but I can still log in to the machine and check the files. I'll make it up later and next time you may just let me update that. |
As a follow-up of data loss issue in Dec 2019, it turns out that a POST request could become a GET request with 301 redirection, this may prevent some clients which are still using Returning 307 code could solve the issue. Also an update for data loss starting from Dec 2020, we've added event and tracing reports in both client side and server side, but for now we don't have any new findings yet |
@KagamiChan it seems quests are not being reported? https://api.poi.moe/dump/quests.gz only has January quests and https://api.poi.moe/api/report/v3/known_quests is empty. Also reminding that https://github.com/poooi/poi-server/wiki is missing quest reward dumps, etc. |
@gakada ack, will take a look later |
@gakada There were multiple issues, I've fixed them and restored back some data sets quests should be ready with next daily dump, and I'll add rewards later |
Updated Nov 2024
https://db.poi.moe/
withoutdump
pathnameUpdated Jan 2021
According to poooi/poi#1843, there'll be some changes on the strategy of ship drop data storage and dumping.
The text was updated successfully, but these errors were encountered: