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
It's possible I'm misunderstanding the use case of this package, but I don't think thats the case. I want to use this package in a Lambda function, like any typical NPM package would be used, so Homebrew doesn't really apply in those cases.
How am I supposed to install GraphicsMagick/ImageMagick then?
Error during PDF conversion: Error: Could not execute GraphicsMagick/ImageMagick: gm "identify" "-ping" "-format" "%p" "-" this most likely means the gm/convert binaries can't be found
Looks like we're possibly losing the URL parameters in the process -
A typical signed URL:
https://[BUCKET NAME].s3.us-east-1.amazonaws.com/[PATH]?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=[CRED]t&X-Amz-Date=20241028T214426Z&X-Amz-Expires=120&X-Amz-Signature=[SIG]&X-Amz-SignedHeaders=host&x-id=GetObject
--
Suggestion: User should control the URL input, assuming the URL parameters don't have any bearing on the produced file will lead to exactly this. My use case may be more unique, but even something as simple as https://somewebsite.com/file.pdf?page=3 would likely have conversion on a server to output https://somewebsite.com/file.pdf#page=3 - which is valid pdf url syntax.
It's possible I'm misunderstanding the use case of this package, but I don't think thats the case. I want to use this package in a Lambda function, like any typical NPM package would be used, so Homebrew doesn't really apply in those cases.
How am I supposed to install GraphicsMagick/ImageMagick then?
Error during PDF conversion: Error: Could not execute GraphicsMagick/ImageMagick: gm "identify" "-ping" "-format" "%p" "-" this most likely means the gm/convert binaries can't be found
Node Version: 18.x
NPM version: 10.2.3
Environment: Serverless Offline
Package Version: ^1.0.31
The text was updated successfully, but these errors were encountered: