-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[Deviantart] [Bug] Attempting to download results from a search query with the order set to "newest" only gets the first few deviations #2096
Comments
I'd like to see the output with
Where did you get an |
For some reason I'm now also getting And yeah, it seems to be falling back to something else, but my search results for Also I only just remembered I'm using 1.19.1 because of some changes I made to my local install (exponential backoff and removing the max wait limit; Having too many concurrent downloads causes an infinite loop of 429's). I don't think that matters since the only change to the deviantart extractor was something with stashes in 1.19.2 The (very redacted) output of
|
Wait hang on I'm being a total idiot The 1.19.3 doesn't mention the change to deviantart searching but the commit you linked should be in it. Gonna update and see if that works Edit: Nope, 1.19.3 is still having the issue |
Well, I got 150+ files with that URL before stopping it. Maybe using the And yes, the last relevant change to dA was before 1.19.1, so that shouldn't matter, |
Yeah the case it failed on earlier is working now, but it's still the wrong order which causes issues with A quick test in the developer console shows that Which, given the name and the existence of |
With commit 8f0cf0b it now uses
Immediately stopping when finding an already downloaded file is generally a bad idea and usually causes more harm than it's worth. I'd recommend at least |
I checked if it was a problem with mature deviations but it seems not. the
/browse/newest
API endpoint is definitely returning more deviations than what's being downloaded, but the extractor doesn't seem to use it?This could be related or identical to #1704 and/or #1911
The text was updated successfully, but these errors were encountered: