-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
exception not thrown when truncating filenames longer than 255 char #12076
Comments
Interesting, I don't remember us imposing a 255 character limit anywhere. But maybe it's a part of edit: Oh, hmm, unless it's a musl limitation and it happens there... |
The limitation probably comes from emscripten/system/include/libc/limits.h Line 47 in 2bca083
However it's not clear to me where exactly the truncation happens. |
I looked to make a repro yesterday but didn't manage to make one demonstrating Line 1065 in b1a7889
Line 1047 in b1a7889
I also thought |
hm no, that first library_fs.js just truncated the file contents, not the name. I think what probably happens is that when we create the inode we don't check for the length before filling this struct: emscripten/system/lib/fetch/asmfs.cpp Lines 37 to 38 in b9f357c
|
ah, I just read that asmfs is a work in progress so it's probably not that: #9534 😄 |
so most likely here: Lines 645 to 646 in b1a7889
|
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant. |
From what I can see this is still an issue. |
When files with a filename greater than 255 characters is being created, it is truncated, but does not throw an exception that other systems throw.
Expectation: File is truncated and created with an exception thrown.
The text was updated successfully, but these errors were encountered: