In some situations, I've observed make
below to fail for lack of a locatable libpcre2:
v=10.36
wget https://downloads.sourceforge.net/pcre/pcre2-$v.tar.bz2
tar -xvjf pcre2-$v.tar.bz2
pushd pcre2-$v
./configure --prefix="$HOME"
make
make install
wget https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.0p1.tar.gz
tar -xvzf openssh-8.0p1.tar.gz
cd openssh-8.0p1
./configure --prefix=$HOME --with-privsep-path=$HOME/var/empty
make
make install
The --with-privsep-path=$HOME/var/empty
is necessary to avoid an error like:
from os import chdir, getcwd | |
from pathlib import Path | |
class cd: | |
"""Context manager for changing the current working directory""" | |
def __init__(self, path): | |
path = Path(path) | |
self.path = path.expanduser() |
Supplemental to Kubeflow Pipelines' docs about using Minikube.
See Minikube docs.
The repro in shapeless#902 above is very simplified from my real use-case; perhaps I should just do something different upstream to avoid this, but nevertheless that behavior seems unexpected.
More context on my real use-case, fwiw:
A
is actually OHList
("Options HList"), where each element in the underlying HList
is wrapped in Option[_]
, and some relevant functionality is exposed.TC
is actually a comparator type-class Cmp
, which defines logic for determining whether two instances of type T
are equal:
Δ
representing the computed diff.
trait Cmp[T] { type Δ; def apply(l: T, r: T): Option[Δ] }
gcloud services enable composer.googleapis.com
gcloud config set composer/location us-east1
# Cloud Composer "environment" name
ENV=…
# Create Python3 Environment
gcloud composer environments create $ENV --python-version=3
# Describe Cloud Composer environment, or specific fields:
gcloud composer environments describe $ENV
gcloud composer environments describe $ENV --format="get(config.dagGcsPrefix)"
git config --add remote.origin.fetch '+refs/pull/*/head:refs/remotes/pr/*'
git fetch origin
git checkout pr/123
Helper scripts for spinning up Kubeflow clusters and monitoring them as they boot up.
An embellished version of the commands recommended in the docs:
export KFAPP=<YOUR CHOICE OF APPLICATION DIRECTORY NAME>
${KUBEFLOW_SRC}/scripts/kfctl.sh init ${KFAPP} --platform gcp --project ${PROJECT}
cd ${KFAPP}
${KUBEFLOW_SRC}/scripts/kfctl.sh generate platform
I was trying "Run the tests", and saw some failures, apparently due to having GCC linked under gcc
/g++
instead of clang, on macOS:
ERROR: /private/var/tmp/_bazel_ryan/b82c47e810a34e3560644976a9c6bf6f/external/protobuf_archive/BUILD:626:1: Linking of rule '@protobuf_archive//:python/google/protobuf/internal/_api_implementation.so' failed (Exit 1)
gcc: error: unrecognized command line option '-fobjc-link-runtime'; did you mean '-fgnu-runtime'?
Specifying clang
in the CC
env var seemed to work: