You must log in or register to comment.
Do you have a copy of the image you were trying to upload? I could check the logs to see what’s wrong.
Image uploads seem fine on my end:
Except for some really large (8000x8000) images. I also upgraded to a pre-release of pictrs last night because it fixes this really annoying bug where images appear broken. But it might have introduced other bugs.
The original from this https://yande.re/post/show/253713 I didn’t realize the size, but the error is pretty cryptic if that was why. Thanks for checking
Size: 4726x6734
That might be the case. I think I can increase the limits that pictrs can accept.
edit: I increased the limits so very high resolution images (up to 8000px) can be uploaded (but are still downscaled to 4096px).
Now, what I can’t figure out is why pictrs isn’t processing the Haruhi image. Directly uploading the file taken from yande.re doesn’t work (it just silently fails). Converting the file to PNG (or any format) and uploading works:
I shall investigate more.
Could it be that it doesn’t handle images encoded as YCbCr4:4:4?
After extensive testing, I might have figured it out.
Any JPEG image with truecolor, 100% JPEG quality, and >5 megapixels silently fails. It’s very specific but I’ll see what else I can do.
edit: I think I figured it out (again). Lemmy has a timeout of ~30s for images. It takes more than 30s for pictrs to process a JPEG image with the properties above (about ~45s). The image will be processed and can be accessed via its URL but Lemmy won’t return the URL because of the timeout. The timeout is actually hardcoded to 30s. I’m not sure why it’s hardcoded nor do I understand why it takes pictrs to process the image for so long (it only takes a second when I do
magick convert image.jpg image.webp). I assume this is why videos don’t get processed either when I tested some time ago. Anyway, I’ll try to bring it up with the devs.
Probably the image is too large.
Lemmy still has a few cryptic error messages.I can’t test as I don’t have an account on your instance, but that message shows up sometimes when the image is too large.
It seems intermittent, so perhaps the server is just overloaded.
