FANBOX: Filename too long causes Invalid Argument

[shinji257]

Prerequisites

• Did you read FAQ section in readme.md?
• Did you test with the latest releases or commit ? Release version
• Did you search for existing issues in Issues?

Description

When the filename ends up being too long due to a really long title it causes Windows to throw error 22 (Invalid Argument) messages and it fails to continue. I believe this is a return of an old bug from 2019 #525

Steps to Reproduce

1. Run PixivUtil2
2. Choose F3 (specific post)
3. Enter post 2277564

Note that post is very much NSFW and require support to get.

Expected behavior: Filename either remove title or truncated

Actual behavior: Errors as logged.

Log file:
pixivutil.log

Versions

PixivDownloader2 version 20220924

[Nandaka]

you can try to enable long filename/path support in win10
https://www.itprotoday.com/windows-10/enable-long-file-name-support-windows-10

[shinji257]

It's already enabled for me.

[Nandaka]

weird, it is working in when I try from python console.
Is your target drive formatted using NTFS? Long filename only supported if you are using NTFS, I think?

https://github.com/Nandaka/PixivUtil2/blob/master/PixivHelper.py#L764

[shinji257]

I'm actually using a network drive so maybe it is samba not supporting but the network host is Linux. It should be fine (in theory). Anyways I'll try this post on a local location with ntfs and see if the issue goes away and update this with the result when I do.

[Nandaka]

ok, it is kinda similar with my case, but the Z: drive is actually another win10 shared folder.

[shinji257]

Ok. It works fine on a local NTFS formatted drive, but it won't copy to the network drive.

EDIT: Just to clarify it won't copy via any means (but reducing the length by 12 did let the files copy over) so it isn't a PixivUtil2 specific issue but I'm leaving this open in case you want to do something about it at all.

[shinji257]

So just a small update. This is due to Linux path limitations since the SMB share is hosted there in the end. Just to double check I had zipped the affected files up, uploaded to the server, then tried to unpack (via a shell -- not SMB) and same error. The same issue may not present itself on a Windows based SMB share and is not a SMB issue.