libcurl link-time ssl backend (openssl) is different from compile-time ssl backend (nss)

[khawerrind]

Hi, i have been getting the following error all of sudden. I have deployed serverless-image-handler 5 months ago but today i have been getting these errors. Any fix to this?

[ERROR]	2019-07-24T15:32:22.835Z	bc30e8c3-3bc8-4a35-aa4a-f5d2723c5788	start_thumbor trace: Traceback (most recent call last):
File "/var/task/image_handler/lambda_function.py", line 202, in start_thumbor
importer = get_importer(config)
File "/var/task/thumbor/server.py", line 69, in get_importer
importer.import_modules()
File "/var/task/thumbor/importer.py", line 53, in import_modules
self.import_item('LOADER')
File "/var/task/thumbor/importer.py", line 97, in import_item
module = self.import_class(conf_value, get_module=True)
File "/var/task/thumbor/importer.py", line 43, in import_class
return import_class(name, get_module)
File "/var/task/thumbor/importer.py", line 19, in import_class
module = get_module and __import__(name) or __import__(module_name)
File "/var/task/tc_aws/loaders/s3_loader.py", line 14, in <module>
from ..aws.bucket import Bucket
File "/var/task/tc_aws/aws/bucket.py", line 9, in <module>
from tornado_botocore.base import Botocore
File "/var/task/tornado_botocore/base.py", line 29, in <module>
AsyncHTTPClient.configure("tornado.curl_httpclient.CurlAsyncHTTPClient")
File "/var/task/tornado/httpclient.py", line 289, in configure
super(AsyncHTTPClient, cls).configure(impl, **kwargs)
File "/var/task/tornado/util.py", line 354, in configure
impl = import_object(impl)
File "/var/task/tornado/util.py", line 181, in import_object
obj = __import__('.'.join(parts[:-1]), None, None, [parts[-1]], 0)
File "/var/task/tornado/curl_httpclient.py", line 23, in <module>
import pycurl # type: ignore
ImportError: pycurl: libcurl link-time ssl backend (openssl) is different from compile-time ssl backend (nss)

[mc962]

I just noticed this too (with Serverless Image Handler v3 I think)

[soupy1976]

AWS updated the lambda execution environment which has caused this problem with the v3.0 implementation. You have two options:

i) Someone has just posted a fixed up version of 3.0 which they say works in the new lambda environment - See here: #127

ii) Do what I did, and fix up the new SharpJS version 4.0 so that it works with Lambda style requests. See here: https://stackoverflow.com/questions/57178748/aws-serverless-image-handler-v3-x-broken-by-changes-to-aws-lamdba-execution-envi

[khawerrind]

I have upgraded to v4. Thank you!