-
Notifications
You must be signed in to change notification settings - Fork 22
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
Submission stuck in pending state #70
Comments
I have noticed the same phenomenon with multiple clients since beginning of 2022. Old submissions are stuck as well as new ones. The statistics page at acoustid.org shows that there are additions. Is anyone able to get submissions through? |
@lalinsky That submission is still pending. Another newer one is submission 626731807 (see also this discussion). I'd suspect there are quite a few submissions stuck in pending by now. Can there be anything seen why they are stuck? |
I'm also having this problem. No acoustIDs I've submitted via Picard since yesterday get through, and when I query the API they show up as Pending. Example: https://api.acoustid.org/v2/submission_status?client=v8pQ6oyB&clientversion=2.8.4&id=655022136 Contrary to earlier times when AcoustID has had problems, the processing is not reported as 0, the stats page is reporting that acoustIDs are being processed. https://acoustid.org/stats EDIT: I tried generating a new API key. It works for me now! |
I've been having this issue for about a week, changing keys/accounts/IP had no effect. |
@severincognito Can you get me an ID that is pending? I see submissions being processed OK. |
This still occurs -- I thought it could be some temporary issue on the server (or server cache). If so, it's a timeout longer than 2 weeks. I tried again with two accounts / new keys, picard 2.8.5 & 2.9.0b, ... everything is still pending forever. |
Is there anything else I can do to help debug this? the picard -d log isn't sending any more helpful information besides the "pending" result of the API call. |
I've submitted a bunch of tracks that have this same issue. When the service is working most tracks get processed just fine but some end up getting 'stuck' for days, months or even years. Example - this track I've submitted repeatedly over a very long period and it never processes for some reason: I have others where the audio starts with a prolonged section of silence, and the fingerprint doesn't generate correctly it seems. |
@lalinsky here is another case that might be interesting https://api.acoustid.org/v2/submission_status?client=v8pQ6oyB&id=693297919 One specifically interesting part might be that the submitted fingerprint matches https://acoustid.org/track/419210c2-28a4-4409-bced-c8e4741b3d15 , but was submitted with a different length. Submitted was 263, the one one present on the AcoustID recording has 277, so above the 7 second similarity threshold. Maybe this is related to why some fingerprints never get processed and end up pending? In case it is helpful this is the fingerprint:
|
I care about this too. |
This issue keeps popping up. We got a report at PICARD-2932 which has two additional submissions being stuck in pending: https://api.acoustid.org/v2/submission_status?client=rxygmyT9vo&id=712451957 Here are the submitted details:
|
I still can't submit anything, either through Picard or using the API directly. Everything stays pending. I really would like to contribute to the database, but until this is fixed I can't do anything. |
Any hopes this will ever get fixed? Is there progress being made? I submitted AcoustID fingerprints back in 2022 and they're still in pending state. |
The submission https://api.acoustid.org/v2/submission_status?client=qkL7OGeRlR&id=602773672 and other submissions for this fingerprint are not being processed. E.g. submission 602889786 is for the same fingerprint, and also stuck.
Is there still some general issue with submissions, or is this something specific to this fingerprint?
See also the discussions at:
https://community.metabrainz.org/t/acoustid-issue/547046/24
https://community.metabrainz.org/t/performance-issues/545370
The text was updated successfully, but these errors were encountered: