Skipped file filenames replaced with "?" in console if matched to sqlite archive entry

[biggestsonicfan]

Not sure if this was intentional to reduce overhead, but I'd prefer an option to see the full filenames if they're matched and not "guess" at what in the gallery was matching and if it was correct or not. Someone with an incorrect archive setup would have no idea what they were missing. Using latest from git.

[kattjevfel]

The thing is that the filename isn't stored in the database, usually it's just the post ID or similar, so it has to "guess", instead of looking it up (which would miss the point of using the database in the first place).

[biggestsonicfan]

That's never stopped gallery-dl from displaying the currently configured formula for filenames before, regardless if it's the actually saved file name or not. Hiding all information rather than displaying what it can is not an ideal situation, especially when trying to diagnose issues. Issues like if a post id has two attachments with identical filenames in it and the archive isn't set up to numerically increment attachments.

I am currently using the database to split my gallery archives across multiple drives, so they have different file paths, but duplicate files won't be downloaded. Again, no, I am not saving enough information to re-generate the filename in the archives themselves, but it would be nice to see which information I have configured (dates, post ids, file names, titles, etc) display as they are skipped.

Seeing thousands of '?' as they are skipped when using a batch file with -i doesn't help me understand how far gallery-dl is progressing until it just suddenly reaches the next line in the batch file.

I can't imagine this change was made lightly, as it had been this way since as far as I can remember, but I can't find the discussion, pull request, issue, or commit for the change. I'd like to see the reasoning behind it.

[wlritchi]

I believe this is the same as #3362

[biggestsonicfan]

I believe this is the same as #3362

Ah, yup, so it is known and marked as regression. Closing as dupe. 😅

[biggestsonicfan]

Whoops, looks like I could only close as "completed" or "not planned" via the GitHub app. You can't just "close" an issue anymore? Huh...