python-build | A simple , correct PEP517 package builder

I uninstall anaconda and my problem went away.

It turns out that the install_repreqs.sh has been updated and I forget to rerun it. After installing the prerequisite by rerunning install_repreqs.sh, I can build drake from source successfully.

When x_cf_routererror says endpoint_failure it means that the application has not handled the request sent to it by Gorouter for some reason.

From there, you want to look at response_time. If the response time is high (typically the same value as the timeout, like 60s almost exactly), it means your application is not responding quickly enough. If the value is low, it could mean that there is a connection problem, like Gorouter tries to make a TCP connection and cannot.

Normally this shouldn't happen. The system has a health check in place that makes sure the application is up and listening for requests. If it's not, the application will not start correctly.

In this particular case, the manifest has health-check-type: process which is disabling the standard port-based health check and using a process-based health check. This allows the application to start up even if it's not on the right port. Thus when Gorouter sends a request to the application on the expected port, it cannot connect to the application's port. Side note: typically, you'd only use process-based health checks if your application is not listening for incoming requests.

The platform is going to pass in a $PORT env variable with a value in it (it is always 8080, but could change in the future). You need to make sure your app is listening on that port. Also, you want to listen on 0.0.0.0, not localhost or 127.0.0.1.

This should ensure that Gorouter can deliver requests to your application on the agreed-upon port.

pyenv requires some packages to build Python from source.

For Ubuntu, from pyenv wiki: suggested build environment

Try env ARCHFLAGS="-arch x86_64"

(that works for me for other Python-related tools, I don't use pyenv myself).

Rationale: modern macOS supports 2 architectures: intel (x86_64) and m1 (arm-something). Compiling for only one architecture is easier.

Fixed by installing the package properly in the builder image:

Yes, BoringSSL is used for all grpcio pre-compiled wheels. However, not all of them enabled assembly optimization for encrption: https://github.com/grpc/grpc/blob/master/doc/ssl-performance.md

Building with OpenSSL is an option that people need to explicitly opt-in: https://github.com/grpc/grpc/blob/master/setup.py#L138

These are the relevant parts of your log:

Upgrade your python to at least 3.6

That version of pip doesn't support version 3.5 as the older python version doesn't include f-strings which were introduced in 3.6.