You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generating e.g. .png badges from the CLI or API will fail silently when imagemagick is not installed. An empty .png is emitted.
Expected behavior from the CLI: an error return status and an error message. From the API: an error message in the response, a 503 status code, and a log message.
This was a gotcha for me, and would be for other people getting set up as well: see #883.
The issue is upstream issue in gm. When spawning convert, this line invokes the callback immediately, before the subprocess has a chance to emit the error.
Reported at aheckmann/gm#548aheckmann/gm#256 but there hasn't been a fix. Not much active maintenance on that project, unfortunately.
Some possible resolutions:
Fix upstream (seems best)
Raise an error when nothing gets emitted (seems a serviceable hack)
Run a quick self-test when the server starts up (seems worst)
The text was updated successfully, but these errors were encountered:
Given the chunks coming from imagemagick are getting stored memory and
then tucked into a cache, this function could as easily return a buffer
via callback. Streaming is just making it more complex. (And trickier to
test!)
Generating e.g. .png badges from the CLI or API will fail silently when imagemagick is not installed. An empty .png is emitted.
Expected behavior from the CLI: an error return status and an error message. From the API: an error message in the response, a 503 status code, and a log message.
This was a gotcha for me, and would be for other people getting set up as well: see #883.
The issue is upstream issue in gm. When spawning
convert
, this line invokes the callback immediately, before the subprocess has a chance to emit the error.Reported at
aheckmann/gm#548aheckmann/gm#256 but there hasn't been a fix. Not much active maintenance on that project, unfortunately.Some possible resolutions:
The text was updated successfully, but these errors were encountered: