Installing Gunicorn using Cygwin - linux

How can I install Gunicorn using Cygwin?
I cant seem to find the Gunicorn Package on Cygwin...Unless I'm understanding the issue on github wrong, I think it does support Gunicorn.
Also I found this in the changelog:
0.17.2 / 2013-01-07
optimize readline
make imports errors more visiblle when loading an app or a logging class
fix tornado worker: don’t pass ssl options if there are none
fix PEP3333: accept only bytetrings in the response body
fix support on CYGWIN platforms

Related

#tensorflow/tfjs-node: sudden craving for aws-sdk, nock, mock-aws-s3

System information
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Ventura 13.2.1
TensorFlow.js installed from (npm or script link): npm
TensorFlow.js version: 4.2.0
Describe the problem
I had previously used the #tensorflow/tfjs-node library successfully with no issues. Now, however, I have changed environments and unfortunately I am running into issues. I don't have the original source code any more to compare to see what the difference is.
I am running under node v18.4.0, although I have tried v16.16.0 and v14.21.2 (using nvm on macOS).
The problem is now it seems the library wants all sorts of supporting modules, which are not installed:
aws-sdk
nock
mock-aws-s3
It will not build without these, so I npm i them and then it builds happily.
So first question: why might my environment now be needing these where it didn't need them before? What might be different? As I say, sadly I don't have the last environment around any more.
Having built this, I now receive the error:
Error: #package/learn package.json is not node-pre-gyp ready:
package.json must declare these properties:
binary
Although I could configure all this, I think it is the wrong thing to do, since I had it up and running previously without any of this. Is where are these issues now coming from?
Can I run the #tensorflow/tfjs-node without installing or needing those three dependencies? I can provide the other config if it is not apparent to someone who has had the same issue.

Ignore warning for certificate verification during HTTPS Rest call

I know this has been asked and answered many times: Reenable urllib3 warnings,
How to suppress warnings about lack of cert verification in a requests HTTPS call?
Even I had it working as well previously with below solution:
import requests
requests.packages.urllib3.disable_warnings()
But since I had enabled extension for pyLint in VSCode it stopped working.(I know pyLint may not have impacted it but I have started facing this only after enabling pyLint extension)
So pyLint started complaining about "packages" is not there in "requests"
I have tried another solution being discussed in above posts, which is:
import urllib3
urllib3.disable_warnings()
Which doesn't work as well.
Someone also suggested to use
requests.urllib3.disable_warnings()
instead of
requests.packages.urllib3.disable_warnings()
but in my case it seems "requests" doesn't have "urllib3" inside it.
So is there any other way to ignore these warnings.
I am having below setup:
Python - 3.10.6
requests - 2.28.1
urllib3 - 1.26.12
pyLint extension for VSCode - v2022.4.0

Google App Engine: cv2 libSM.so.6 error on Flask app

I have a Flask app that I want to deploy on the Google App Engine. Everything checks out fine, the requirements file contains all the modules which get installed successfully. But towards the end I get this error:
from .cv2 import *
ImportError: libSM.so.6: cannot open shared object file: No such file or directory
I read on various blogs and other similar stackoverflow questions that you need to install libsm6 using:
sudo apt-get install libsm6
But even after I did that, I still get the same error. How do I solve this?
The App Engine runtime has a fixed set of system packages that are included in the runtime and unfortunately libsm6 is not one of them. In addition, it's not possible to install additional system packages.
However, this is an ideal use case for Cloud Run, which lets you define your own runtime via a Dockerfile. See the quickstart for an example: https://cloud.google.com/run/docs/quickstarts/build-and-deploy

Secure Gateway client not starting on Linux

I have installed the Secure Gateway client (v1.4.2) on RHEL V7. When I attempt to start the client, I receive an error that log4js cannot be found. I am trying to find out where log4js should reside.
enter image description here
Additional information:
Installation was done as follows:
rpm -ivhf ibm_securegateway_client_1.4.2_x86_64.rpm --force
Hardware: Intel (not AMD)
The installation log indicated that the install was successful.
Please add --force option on Redhat Version 7.
rpm -ivhf --force ibm-securegateway-client-1.4.2+client_amd64.rpm
It looks like your node modules did not install correctly. Please ensure you have the correct permissions and reinstall so the node modules can be correctly added.
On a side note, you may encounter issues when attempting to start the client from outside the client directory due to how it searches for the associated files.

NPM / gyp error when installing redis

Full error/warning log: http://pastebin.com/xNjC4FDr
I had problem as well when I tried to install MongoDB, I have made SO question of it but, that was only warnings, so I could ignore it. But this time it's not only warnings, but also red error.
What do I have to do? Is my Nodejs messed up because I've installed Visual Studio Tools for NodeJS in the past? Or is this normal behavior? What can I do about this, I prefer not to see errors/warnings when I install something on NPM.
The problem is that hiredis does not support Windows currently. The link to the Windows-compatible fork in the hiredis readme seems to be outdated (last commit in 8/2013 as of this writing), so you may be out of luck.
However hiredis is not required by the redis module, it's an optional dependency that just makes parsing the redis protocol faster than the pure JavaScript parser that is bundled with redis. You may see a similar thing with other modules that have optional dependencies like this. Typically if you see the module tree outline at the end of the console output, that means the module installation was successful.

Resources