-
-
Notifications
You must be signed in to change notification settings - Fork 349
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
[bug] Some pngs give error error decoding image: image: unknown format
#2340
Comments
Ah interesting, yep I can replicate it on latest snapshot. Looks like an issue with the library we use for detecting file formats. EDIT: actually it looks like the error is coming from Go's EDIT2: or the file is not being put into storage at all, which is why it can't be decoded afterwards, I'll have to poke at this |
Ah interesting, I tried downloading the image to my own computer from that instance, then uploading it as a media attachment on a locally-running GtS instance, and I get the same error... |
tobi dixit:
Ah interesting, I tried downloading the image to my own computer from
that instance, then uploading it as a media attachment on a
locally-running GtS instance, and I get the same error...
I also had a video today that wouldn’t show up but was viewable from
the remote instance; should I hunt that down so you have more examples
of misdetected media?
bye,
//mirabilos
|
No that's fine, thanks. We've already got a fix for that sort of issue in the works. |
error decoding image: image: unknown format
Bit more of a writeup on this after looking at it a bit more: The reason it returns In other words: the png was not stored, but nor did writing 0 bytes into storage return any errors. I think the reason it's not being stored is because exif terminator is overzealously terminating the entire image as it's being streamed into storage. I'll have to do a bit more investigation of this to determine why that is the case. Doesn't make a lot of sense for it to do that, so I'm assuming it's a bug either in exif terminator, or in the png structure library that exif terminator depends on. |
Got a fix for this in the works now: superseriousbusiness/exif-terminator#6 |
Describe the bug with a clear and concise description of what the bug is.
I was just looking at logs and:
Well…
file(1)
knows it as…… and
xloadimage
displays it just fine.What's your GoToSocial Version?
0.12.1 git-5fdc005
GoToSocial Arch
amd64 binary
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: