-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
importing takes a very long time with discogs plugin enabled #4108
Comments
Additionally to the issue with the high waiting time, I am also noticing how there are no results obtained from My first question therefore is: what is the program doing for 4+ minutes instead of scraping Second question: what happens when I use
|
Hmm; is there any chance the Discogs search APIs are/were down or inaccessible? That seems like the simplest explanation for searching Discogs being slow and returning no results… |
the discogs api itself is working fine (as in reachability) as it can be seen when passing also I would expect any issue where the API is down or inaccessible to print some error message on console (if not from beets, from the library being used) but here nothing shows up at all please let me know which other info you may need to triage this |
Certainly, but what I meant to ask was whether the search API specifically, rather than the ID lookup API, might be down. I can think of two ways to start trying to narrow this down:
|
When I use
good point, from the command output it's not clear where the command hangs, it always happens after will try adding some print statements to the plugin and see what else happens |
well I guess it was rather easy to find the source of the problem, all I needed was to add a simple statement there
then I ran import again and...
my problem now is that I have not a clue of where to start to fix this, if someone could help/take care of this I would be extremely grateful. |
also curious of how this was not caught by any test, unless clearly there is no test case for it :) |
after further digging this has been introduced in PR #3138 |
As we are using python3-discogs-client and the rate limiting function has been released as follows Access remaining rate limit, we should review how we can leverage the rate limiting native function rather than a random wait between calls. Rate limiting enabled by default. Looks like a simple fix to remove the rate limiting included in #3138 |
That's a good idea, @arogl! |
Problem
Whenever I want to import something in my library and I have Discogs enabled as a source, import operation can hang for various minutes while attempting to retrieve Discogs information.
Here is an example with discogs enabled
Compared to the same import without discogs plugin enabled:
Setup
My configuration (output of
beet config
) is:This issue is reproducible on any instance and I don't believe it being tied to my specific configuration file, the relevant discogs section just contains the token
The text was updated successfully, but these errors were encountered: