:be: I really really really wish you gous wouldn't set tickets as "fixed" until tey are on beta so i cna test them. becasue if they are set as fixed I know ,they aren' testable yet until .. some later time .. and by then i've forgotten
đ I really really really wish you guys wouldn't set tickets as "fixed" until tey are on beta so i cna test them. becasue if they are set as fixed I know ,they aren' testable yet until .. some later time .. and by then i've forgotten
like it's been idk almost a week since "enter doesnt do anything" on BB was "fixed"
Hello! I recently uploaded about ~70000 listens to listenbrainz via the pylistenbrainz utility. The listens all seem to be there (paging through the history), but even after a day, the total at the top of the page still shows the amount of listens prior to the import, and the stats haven't updated. I imagine it takes some time to propagate through
the (backend?), but just out of curiosity, I'm wondering if anyone here has any insight into what's going on behind the scenes. (e.g. are stats refreshed on a recurring basis?)
sumedh has quit
FWIW, I also tried to delete all of my existing listens prior to the import and they never seemed to go away, either. So, I'm wondering if a combination of things I did borked something.
_lucifer
petricordial, when did you update the listens? by the total at the top of the page do you mean the listen count?
petricordial
1) I deleted old listens + updated new listens about noon (ET) yesterday, I'd say. 2) The bit that says "Recent listens (10145 total)". I'd expect it to be anywhere from 70000-80000 depending on if the deleted listens were retained or now.
not*
_lucifer
also the stats are refreshed daily. thanks for the report. its something wrong on our end. it seems the dumps are borked are again/
Let me know if there's any additional information I can give! I have all of my data + the pylistenbrainz upload script in a public repo if that's worth anything.
_lucifer
can you share your username so that we can take a look?
the listen count logic was recently updated so it might we missed something.
thanks!
petricordial
:> !
_lucifer
you also mentioned some issue with listens deletion. what was it?
petricordial
Oh! I just tried to delete my listens and noticed that the ~10000 number didn't change, whereas I'd expect it to go to 0. I didn't actually page through all my listens to investigate, though. (I sort of did all of the steps at once, so it's hard to say which actions caused which results. Hindsight is 20/20... oops.)
The ~10000 was roughly what it was at before I did anything, I think.
_lucifer
i checked the db, it shows you have ~60 K listens. so there's probably something wrong on our side as well.
how old were the listens you submitted using the script?
petricordial
2009 - 2020.... Though, now that I think about it, the listens from 2018-2020 were likely duplicates (i.e. I think they were already on Listenbrainz through an older last.fm import), so the 60k number would make sense if duplicates were caught.
Oh! I have one other thing to report, I think.
_lucifer
thanks, that info'll help narrow down the possible issue.
petricordial
I got an HTTP 504 Gateway Timeout when I tried to upload all 70000 in a single batch (using pylistenbrainz's `submit_multiple_listens`). So, I tried splitting my submissions into smaller batches of 100, which worked OK.
It might be nothing, but I thought I'd mention it.
_lucifer
interesting, i'd not expect a 504 but another reasonable error if the total payload size exceeded the allowed size.
ruaok
_lucifer: sigh. Check /dumps/dumps.log (IIRC) in the cron container and see what is up.
_lucifer
ruaok: yeah, just did that. it is unable to create the dump file it seems.
mktemp: failed to create directory via template â/mnt/dumps/tmp/archives/incremental.XXXXXXXXXXâ: No such file or directory
petricordial: thanks again for all the info and the report. i have opened a ticket here for the listens count issue LB-884.
_lucifer: Thank you for all the hard work you do! I'm very grateful for the efforts of the *Brainz communities :)
_lucifer
feel free to add more details there :). also since you mentioned you have the data a public repo, please share that as well. i'll try to reproduce the 504 issue.