-
Notifications
You must be signed in to change notification settings - Fork 345
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
MiniMagick::Invalid 'identify' doesn't return a description for failed with error: #471
Comments
Could you give me more information, at least the image for which this error happens? Ideally you should give me everything I need to be able to reproduce the issue, including the image and a minimal self-contained example that reproduces the issue. E.g. your example shows |
This might be related to an issue I'm having processing PDFs like this:
I get this error:
I fixed a similar issue with ImageMagick that came up randomly where specs were failing to process PDFs on Codeship by adding the PDF filetype to the ImageMagick policy before my builds:
However, doing this on Heroku hasn't fixed the problem, it looks like I'm missing a libIlmImf dependency? |
Am using minimagick to prepare files for print. There is no one particular image that is returning this error. The error is happening on every file that I try to output. My current suspect now is that there's no file for minimagick to read. What I can't figure is how this started happening out of the blue and why it's persisting.
Sentry:
|
I came across a similar issue the other day, but with the convert command: image.composite(main_image.resize_to_fill(680, 482).call, gravity: 'north', offset: [5, 1268]) Exception on (app-name): The error message was blank. We have it configured to retry jobs such as this, and the second time (with same exact params) it worked just fine. I've only come across this once so far, but did find it strange that there was no failed with error message and that it was successful with no changes the second time around. Probably not enough to go off of, but since it seemed to be an intermittent thing I'm not sure I can reproduce. |
Having the same issue with img = MiniMagick::Image.read(data)
MiniMagick::Invalid (`identify /tmp/mini_magick20190606-21762-bt22qgsvg` failed with error:)
identify: no decode delegate for this image format `' @ error/constitute.c/ReadImage/501. Requires img = MiniMagick::Image.read(data, '.SVG')
#<MiniMagick::Image:0x000000000ea335a0 @path="/tmp/mini_magick20190606-21762-b0i29q.svg", @tempfile=#<Tempfile:/tmp/mini_magick20190606-21762-b0i29q.svg (closed)>, @info=#<MiniMagick::Image::Info:0x000000000ea33578 @path="/tmp/mini_magick20190606-21762-b0i29q.svg", @info={}>> |
Having a similar problem to the OP with the attached file.
Example:
|
This is the stack trace of such an error - not sure if it's helpful @janko
|
@alex-benoit Thanks, but unfortunately it doesn't tell me much why the error happens. So far it seems that the ImageMagick command is simply returning a nonzero exit code without any error message, which isn't something MiniMagick can do anything about – it would need to be fixed in ImageMagick itself. I'm open to be proven otherwise. It could also theoretically be a bug in Ruby where it doesn't correctly stream the stderr of the ImageMagick command back to our Ruby program. But I'd prefer not to consider that option 😛 In order to debug this issue, I would need:
I've tried reproducing #471 (comment), but no error happened when I tried to execute it. I'm on Mac OS with the following ImageMagick installation:
|
I'm having this issue in Ubuntu. I read in svg in XML format and convert it to an .png file. It works fine on my Mac tho. Not really sure if it's @wilkosz did you find a solution? Update: |
I just upgraded to Catalina and started having this issue with the blank error message. I had a co-worker try it also on Catalina and they were able to see an error message - some ghostscript error. I tried reinstalling ghostscript and that error stopped happening for me. Might be worth a shot? |
Running into this problem both on Catalina and our CircleCI Environment. |
I've solved this problem by switching to |
I experienced the same thing on my Ubuntu server. However, I solved it by installing |
hi, thanks for helping take a look at this.
The closest I found so far is "Getting MiniMagick::Invalid due to improper image header "
Minimgack started failing out of the blue and I can't seem to find the cause of it. Most importantly it doesn't return a description as to why it has failed.
identify /tmp/mini_magick20181016-3982-1mu58uf
failed with error:In my error logs it only shows a 500
MiniMagick::Image.new file.path
MiniMagick::Image.open(node['xlink:href'])
MiniMagick::Tool::Convert.new
Thanks!
The text was updated successfully, but these errors were encountered: