This JPEG seems to fail upload through the API and through web, but possibly with different return codes? Either way, it works fine everywhere else I've tried it.
https://nofile.io/f/q9xBNFU727d/test.jpg
master (If you're a user, don't worry about this).mastodon has a 4mb limit on uploads, and that file is 4.1mb
On Mon, Feb 26, 2018, 3:36 PM Dag Ã…gren notifications@github.com wrote:
This JPEG seems to fail upload through the API and through web, but
possibly with different return codes? Either way, it works fine everywhere
else I've tried it.https://nofile.io/f/q9xBNFU727d/test.jpg
- I searched or browsed the repo’s other issues to ensure this is not
a duplicate.- This bug happens on a tagged release
https://github.com/tootsuite/mastodon/releases and not on master (If
you're a user, don't worry about this).—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tootsuite/mastodon/issues/6566, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAORVxfEsckD_EyFeEzcuCOlX4wNnV-Nks5tYxXCgaJpZM4ST4mK
.
@nightpool It's been 8MB for a long time now
i have another jpeg image that fails to upload (via the web and API) on mastodon.social and octodon.social, with a 502 error. it uploads fine on awoo.space, elekk.xyz, and mastodon.art, however.
Oh, I dunno then. it's probably the nginx max file size config or something.
16,382 pixels is also just ... very long. I wouldn't blame paperclip/imagemagick for choking on it.
Another example: https://nofile.io/f/xXGQCtOPxWS/test2.jpg
This one 502's on mastodon.social, works fine on icosahedron.website.
The problem is, when I generate JPGs on iOS (to convert from HEIF), I end up with these non-working JPGs very often. It is causing serious problems with posting images at all.
imagemagick 7.0.7-28 Q16 seems to have no trouble reading it, either.
4032 x 3024
It's quite big. Perhaps imagemagick is OOM'd on the server you're uploading it to, or the request times out because it takes too long. If that's the case there's nothing I can do right now, and I suggest downsizing the image in the app before uploading.
No, other images of the exact same size consistently went through while
this consistently failed. And mastodon.social should have had enough memory
even then, I’d think?
We added a limit that doesn't allow through images bigger than 4k square pixels so this issue should be moot now