-
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
discogs: Parse IDs from new release URL format #4080
Comments
It looks like discogs may have changed the way they format their URLs? As you can see, we only expect a number after the Lines 212 to 213 in a187739
What happens, for example, if you try pasting just |
That URL didn't work either, but you had me go to regex101 and check the regex being used vs what Discogs uses now [1] versus before [2] and you can see there is definitely a change. Both URLs still work so I guess the regex will need to be updated to account for both? [1] [2] |
Just did a switcheroo of https://www.discogs.com/release/15963324-Larry-Heard-Sceneries-Not-Songs-Volume-One to https://www.discogs.com/Larry-Heard-Sceneries-Not-Songs-Volume-One/release/15963324 and it was able to pick it up
|
Ah, very tricky! Looks like we should make our regex flexible enough to work for both styles of URLs… or else just write two different regexes. |
Problem
at
with no tagsRunning this command in verbose (
-vv
) mode:Then entering
i
to enter release ID, for example: https://www.discogs.com/release/18377836-Aphex-Twin-Come-To-DaddyLed to this problem:
Here's a link to the music files that trigger the bug (if relevant): N/A - any music files will do
Here is some verbose logging while beets was starting up:
Note that the
search
option worked.Setup
My configuration (output of
beet config
) is:I just tried setting my own
discogs.apikey
anddiscogs.apisecret
and I received the samehit rate limit
output as above.Might be worth mentioning that this was working 2 days ago, I hadn't changed anything in my setup between then. My
requirements.txt
file is:The text was updated successfully, but these errors were encountered: