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
BSD sed (as shipped with MacOS) does not support + nor \+ in regular expressions.
However it does support \{1,\} which does the same thing and is also supported by GNU sed.
Moreover, bash 3.2 (as shipped with MacOS) does not seem to support source <(...), it seems to just do nothing.
Using plain eval seems to do the trick though.
Symptom of the former issue is:
source <(setup-envtest use -p env v0.22.1) && go test -race -covermode atomic -coverprofile cover.out ./...
version be a valid version, or simply 'latest' or 'latest-on-disk': unable to parse "v0.22.1" as a version stringshould be X.Y.Z, where Z may be '*','x', or left off entirely to denote a wildcard, optionally prefixed by ~|<|<=, and optionallyfollowed by ! (latest remote version)
And of the latter:
unable to start control plane itself: failed to start the controlplane. retried 5 times: fork/exec /usr/local/kubebuilder/bin/etcd: no such file or directory
(even though the binaries are fetched by setup-envtest)
The text was updated successfully, but these errors were encountered:
BSD sed (as shipped with MacOS) does not support
+
nor\+
in regular expressions.However it does support
\{1,\}
which does the same thing and is also supported by GNU sed.Moreover, bash 3.2 (as shipped with MacOS) does not seem to support
source <(...)
, it seems to just do nothing.Using plain eval seems to do the trick though.
Symptom of the former issue is:
And of the latter:
(even though the binaries are fetched by
setup-envtest
)The text was updated successfully, but these errors were encountered: