from ZIP to bal

Ayubowan! I can build from source and produce the .zip file, but I don't understand the details I still need to do to become able to run 'bal' / 'ballerina'. Estuti.

Ayubowan! Thanks for reaching out and trying Ballerina. You can try downloading pre-compiled packs from this link https://ballerina.io/downloads/. Check here for a quick heads-up https://ballerina.io/learn/getting-started/installing-ballerina/

Rasika, kohomede? Thanks for the hints, however, I forgot to mention that I try building it from source for AArch64, Fedora 33. ./gradlew build works, but what do I need to do afterwards?

hodin innawa :) If you are trying to build Ballerina from source there's another repo called ballerina-distribution you need to build, in-order to get a platform distribution out. This might also need to create a git personal access token (with git packages scope) as below;
export packageUser=<Your github username>
export packagePAT=<Your personal access token>

You can find these instructions in https://github.com/ballerina-platform/ballerina-distribution. Once you built that without any issues, ballerina/build/distributions/ballerina-swan-lake-*.zip will contain the final distribution.
You can extract into a user space and make a soft link such as ln -s /Users/rasika/Documents/WSO2/build_packs/ballerina-swan-lake-alpha2-SNAPSHOT/bin/bal /usr/local/bin/bal to make it work anywhere.
Feel free to reply-back if come across any issues :)

[jw@cn06 jw]$ git clone https://github.com/ballerina-platform/ballerina-distribution ballerina && cd ballerina
Cloning into 'ballerina'...
remote: Enumerating objects: 169, done.
remote: Counting objects: 100% (169/169), done.
remote: Compressing objects: 100% (138/138), done.
remote: Total 64706 (delta 92), reused 59 (delta 27), pack-reused 64537
Receiving objects: 100% (64706/64706), 12.20 MiB | 4.93 MiB/s, done.
Resolving deltas: 100% (43139/43139), done.
[jw@cn06 ballerina]$ export packageUser=LutzWeischerFujitsu
[jw@cn06 ballerina]$ export packagePAT=
[jw@cn06 ballerina]$ ./gradlew build
FAILURE: Build failed with an exception.

Where:
Build file '/data/jw/ballerina/ballerina/build.gradle' line: 63

What went wrong:
A problem occurred evaluating project ':ballerina'.

Could not resolve all dependencies for configuration ':ballerina:jbalTools'.
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Required by:
project :ballerina
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/ballerina-update-tool/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/ballerina-update-tool/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/ballerina-update-tool/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-auth/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-auth/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-auth/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-cache/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-cache/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-cache/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-crypto/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-crypto/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-crypto/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-email/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-email/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-email/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-encoding/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-encoding/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-encoding/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-file/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-file/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-file/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-ftp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-ftp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-ftp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-graphql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-graphql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-graphql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-grpc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-grpc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-grpc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-http/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-http/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-http/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-io/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-io/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-io/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.arrays/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.arrays/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.arrays/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.jdbc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.jdbc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-java.jdbc/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-jsonutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-jsonutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-jsonutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-jwt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-jwt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-jwt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-log/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-log/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-log/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-mime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-mime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-mime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-mysql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-mysql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-mysql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-oauth2/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-oauth2/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-oauth2/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-os/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-os/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-os/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-random/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-random/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-random/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-reflect/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-reflect/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-reflect/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-regex/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-regex/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-regex/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-runtime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-runtime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-runtime/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-sql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-sql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-sql/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-task/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-task/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-task/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-tcp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-tcp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-tcp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-time/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-time/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-time/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-udp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-udp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-udp/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-uuid/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-uuid/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-uuid/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-websocket/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websocket/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websocket/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-websub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-websubhub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websubhub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-websubhub/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-xmlutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-xmlutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-xmlutils/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-xslt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-xslt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-xslt/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/ballerina-openapi/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/ballerina-openapi/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/ballerina-openapi/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinai-transaction/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinai-transaction/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinai-transaction/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/ballerina-dev-tools/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/ballerina-dev-tools/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/ballerina-dev-tools/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-c2c/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-c2c/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-c2c/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-azure.functions/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-azure.functions/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-azure.functions/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-aws.lambda/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-aws.lambda/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-aws.lambda/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerina-docker/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-docker/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerina-docker/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-prometheus/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-prometheus/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-prometheus/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-jaeger/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-jaeger/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-jaeger/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server:
Could not resolve org.ballerinalang:jballerina-tools:2.0.0-alpha3-SNAPSHOT.
Unable to load Maven meta-data from https://maven.pkg.github.com/ballerina-platform/module-ballerinax-choreo/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml.
Could not get resource 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-choreo/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'.
Could not GET 'https://maven.pkg.github.com/ballerina-platform/module-ballerinax-choreo/org/ballerinalang/jballerina-tools/2.0.0-alpha3-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 19s
[jw@cn06 ballerina]$

Usually 401 is returned when the token does not have correct permission. Can you verify whether you have following scope for the token? (you can add those export entries into ~/.bashrc or ~/.zsh)

I'm having progress, but the process appears to be hanging (tried several times):
[jw@cn06 ballerina]$ ./gradlew build
Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details

Task :ballerina:unpackBallerinaJre
Download https://github.com/ballerina-platform/ballerina-custom-jre/releases/download/0.8.0/ballerina-jre-linux-0.8.0.zip
Download https://github.com/ballerina-platform/ballerina-custom-jre/releases/download/0.8.0/ballerina-jre-macos-0.8.0.zip
Download https://github.com/ballerina-platform/ballerina-custom-jre/releases/download/0.8.0/ballerina-jre-windows-0.8.0.zip

Task :ballerina:combineDocs
Combining Docs
docerina: API documentation generation for doc path - /data/jw/ballerina/ballerina/build/target/extracted-distributions/jballerina-tools-zip/jballerina-tools-2.0.0-alpha3-SNAPSHOT/docs

Task :ballerina:buildDistRepo
Building Distribution Repo ...

Task :ballerina:packageDist
Ballerina Tools Distribution Packaged

Task :ballerina:packageDistZip
Ballerina Distribution Packaged

Task :ballerina:packageDistLinux
Ballerina Linux Distribution Packaged

Task :ballerina:packageDistMac
Ballerina MacOS Distribution Packaged

Task :ballerina:packageDistWindows
Ballerina Windows Distribution Packaged

Task :ballerina:testDevToolsIntegration
Created new Ballerina package 'test'.

Compiling source
jw/test:0.1.0
Running Tests
test
[ballerina/http] started HTTP/WS listener <IP_ADDRESS>:9117
[ballerina/http] stopped HTTP/WS listener <IP_ADDRESS>:9117
            [pass] test_addOrderWithoutMock
            [pass] test_addOrderAgain
            [pass] test_findOrder
            [pass] test_addOrder

            4 passing
            0 failing
            0 skipped

Task :ballerina:testExamples
Created new Ballerina package 'test'.

Building example receive-email-using-listener
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example receive-email-using-client
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example send-email
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example secured-service-with-oauth2
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example secured-service-with-jwt-auth
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example secured-service-with-basic-auth-ldap-user-store
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example udp-listener
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example udp-connect-client
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example udp-client
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example tcp-listener
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example tcp-client
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-parameterized-query
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-call-stored-procedures
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-batch-execute-operation
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-execute-operation
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-complex-type-queries
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-query-operation
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example mysql-init-options
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Output Verification jdbc-parameterized-query
Created new Ballerina package 'test'.
Building example jdbc-parameterized-query
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example jdbc-batch-execute-operation
Compiling source
jw/test:0.1.0
Running Tests
test
No tests found
Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Output Verification jdbc-execute-operation
Created new Ballerina package 'test'.
Building example jdbc-execute-operation
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Created new Ballerina package 'test'.
Building example jdbc-complex-type-queries
Compiling source
jw/test:0.1.0
Running Tests
test
            [pass] testFunc

            1 passing
            0 failing
            0 skipped

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Output Verification jdbc-query-operation
Created new Ballerina package 'test'.
Building example jdbc-query-operation
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Output Verification jdbc-init-options
Created new Ballerina package 'test'.
Building example jdbc-init-options
Compiling source
jw/test:0.1.0
Running Tests
    test
    No tests found

Creating bala
target/bala/jw-test-any-0.1.0.bala
Generating executable
target/bin/test-0.1.0.jar
Verify output dynamic-listener
Compiling source
dynamic_listener.bal
Running executable
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  3241  100  3241    0     0  1582k      0 --:--:-- --:--:-- --:--:-- 1582k
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  3259  100  3259    0     0  1591k      0 --:--:-- --:--:-- --:--:-- 1591k
520389090/tcp:
<=====--------> 45% EXECUTING [18m 38s]                                                                                > :ballerina:testExamples
^C[jw@cn06 ballerina]$

Seems like tests are hanging. With all language tests i might get hours to get a build out. Can you also check skipping tests with -x test

That works, and it's fast.
However, which zip file is it in the distribution version that is now to be unzipped (for Linux)? I don't find it.

@LutzWeischerFujitsu you can use ballerina-swan-lake-alpha2-SNAPSHOT.zip. OS specific zips are meant to be used for creating platform specific installers.

Harime hondai, it works. :-)

Niyamai! that sounds great! I'll close the issue since this is sorted now. Please reopen the issue if you need any further help in this regard :)


Feedback for “Secrets Management”

Is it possible to use environment secrets in requirements.txt, e.g. to install a package from a private package repository?
--extra-index-url os.environ.get("PKGIDX_URL_KEY")
mypackage

Hi @somdipdatta,
I think there are two ways it can be done.

You can install package in the notebook, just add code cell with pip command, something like below:

import sys
!{sys.executable} -m pip install git+https://{token}@gitprovider.com/user/project.git@{version}`

We need to fix the order of package installation and secrets provision in the current code and then secrets will work in the requirements.txt. Current code:
https://github.com/mljar/mercury/blob/909fb3fd1186fc4cefac086232183a2ebd80fc08/mercury/apps/nbworker/nb.py#L324-L325
I think we can fix this today and update workers code, I will let you know.

@apjanusz could you please take a look at this issue?

Hi @somdipdatta,
We fixed the problem and updated workers so everything should work.
I tested it with private github repo using github token and everything worked. All you have to do is create a secret and include it in your requirements.txt as ${secret_name}. In moment i will update docs :)
Peace

@pplonski @apjanusz Thanks for your quick action. I just tried it out, works as described!

@somdipdatta no problem :) Here's a link to our docs: https://runmercury.com/docs/pip-install-requirements/
God bless you!


🚀 feat: adds ReplicaSet in Deployments

closes #147
📑 Description
[BE]

Added a new DTO, ReplicaSet, and its helper methods, which will be populated when fetching the details of the deployment.

[FE]

Added a new progress bar which shows how many pods available from the active ReplicaSet in green and all the other pods from non-active ReplicaSet in blue

✅ Checks

[✅] I have tested my code (provide screenshots or screen recordings of a working solution)
[✅] I have performed a self-review of my code

ℹ Additional context

@quest-bot loot #147

Hey @petar-cvit, could you take a look at this and suggest any changes, if any?

@naineel1209, thanks for the PR.
However, I wouldn't have a separate table for replicasets, because Kubernetes will by retain the last 10 replicasets of a deployment

Can we just add a progress bar to the existing pods table that would indicate how many pods are created from each replicaset. For example, if the rollout is in progress and 2 pods are managed from the old replicaset, and 3 are managed from the new one, then 2/5 of the progress bar would be blue (for old pods) and 3/5 is green

Hi @petar-cvit , I’ve updated the ReplicaSet structure to display as a progress bar (check the PR comment for screenshots). The green section represents available pods from the active ReplicaSet, while the blue section shows available pods from non-active ReplicaSets.
Currently, I’m identifying the active ReplicaSet by sorting the list received in the response, using the number of replicas (in descending order) and creation time (in ascending order). If this approach is not favorable, could you suggest any alternative strategies for determining the active ReplicaSet?

@naineel1209 Looks awesome! You can actually find the latest replica in the status.conditions fro a condition of type Progressing and parse the replicaset name from the message. More info on deployment status here. From there, you can check which pods are managed from this replicaset.
I would prefer we infer it from here, not to call the k8s API once more to not bloat the endpoint.
From the UI standpoint, I would remove the numbers on the right since those are not accurate in some cases

Also, I just stumbled upon this issue where pods are still pending and the progressbar is saying 1 active / 1 non-active / 2 total

Hi @petar-cvit, As per the suggestions, In the BE, I've added a new field, activeReplicaSet, in the mapDeployment method which returns us the active ReplicaSet. In the FE, I've added a check to find the active ReplicaSet from the ReplicaSet list. Additionally, I've removed the text on the right to the progress bar and replaced it with a <SyncOutlined spin /> while the replicaset is progressing and <CheckCircleOutlined /> when replicaset is completed, to provide the users with some visual feedback.
Screenshots

@naineel1209 at first, it looked good, but when I restarted a deployment that specified 4 pods, and during rollout, there were six pods (2 from the new replicaset and four from the old one), the progress bar said 3 total, which doesn't match.
Can we make the desired number of replicas in deployment the total, and the green part would tell you how many replicas from the latest replicaset are healthy. If the pods of the new replicaset are unhealthy, they will still show blue.
Also, I would suggest that we don't query for replicasets separately but that we get it from the existing pods. Each pod will have a reference to its replicaset, so we don't have to ask K8s API for it. From there, you can just calculate (number of healthy pods) / (number of desired replicas in the deployment)

Hey @petar-cvit, could you please check out the blocking bug details on Discord? I've got a bug blocking the PR.

Hi @petar-cvit, this PR is ready for review.

hi @petar-cvit, any updates on this one?


Add "Using the EBPF Superpowers To Generate Kubernetes Security Policies" talk

What type of PR is this?
/kind documentation
What this PR does / why we need it:
We now reference the KubeCon talk since the recordings are available on YouTube. The recordings are now sorted by their date, which has been added as well.
Special thanks to @alban and @mauriciovasquezbernal for the great talk!
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report

Merging #1322 (0cdf3af) into main (424a6b5) will increase coverage by 0.06%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1322      +/-   ##
==========================================
+ Coverage   44.16%   44.22%   +0.06%
==========================================
  Files          50       50
  Lines        5627     5632       +5
==========================================
+ Hits         2485     2491       +6
  Misses       3021     3021
+ Partials      121      120       -1


New-Prof Beta Version (hpcprof2)

The (somewhat large) rewrite of Prof, available as hpcprof2{,-mpi}. Supports threads (-j) and runs faster overall (~10x on a large example). Reads DWARF directly and writes the metric-db by default.
Very much a work in progress, there are bound to be bugs (especially in the -mpi version), and not all features are supported (like :StdDev, and CCT reconstruction).
And before Mark says anything, yes, it needs a lot of cleaning. I'm getting there.

For me, it doesn't build.  Is blue42u:prof-2 really the right
branch/commit?
origin  https://github.com/blue42u/hpctoolkit (fetch)

commit 78839d9c0a2f0f8c24620e438258b92079161360 (HEAD -> prof-2, origin/prof-2)
Author: blue42u<EMAIL_ADDRESS>Date:   Fri Sep 13 16:30:08 2019 -0500

    New-Prof, beta version. Available as `hpcprof2{,-mpi}`.

$ ../configure  --prefix=...  --with-spack=...

$ make -j 8

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../src/lib/profile -I../../../src/include -g -O3 -Wall -I/home/krentel/prof2/hpct
oolkit/build/../src -I/home/krentel/prof2/hpctoolkit/build/src @VALGRIND_IFLAGS@ -I/home/krentel/Spack/install/linux-fedora26-x86_64/gc
c-7.3.1/elfutils-0.178-vy75wx77wk2alxqmu7cevb62qa4z4ksq/include -fopenmp -MT libHPCprofile_la-futex-detail.lo -MD -MP -MF .deps/libHPCp
rofile_la-futex-detail.Tpo -c ../../../../src/lib/profile/util/futex-detail.c  -fPIC -DPIC -o .libs/libHPCprofile_la-futex-detail.o
gcc: error: VALGRIND_IFLAGS@: No such file or directory
make[3]: *** [Makefile:679: libHPCprofile_la-futex-detail.lo] Error 1
make[3]: *** Waiting for unfinished jobs....

It looks like you've mixed up some combination of branches.  The make
line uses @VALGRIND_IFLAGS@, but configure makes no mention of
valgrind.
$ grep -i valgr configure*

Also, autoreconf has a lot of errors.  This should never be the case.
src/lib/analysis/Makefile.am: installing 'config/depcomp'
src/lib/profile/Makefile.am:73: warning: source file 'stdshim/shared_mutex.cpp' is in a subdirectory,
src/lib/profile/Makefile.am:73: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
src/lib/profile/Makefile.am:73: warning: source file 'util/futex.cpp' is in a subdirectory,
src/lib/profile/Makefile.am:73: but option 'subdir-objects' is disabled
src/lib/profile/Makefile.am:73: warning: source file 'util/futex-detail.c' is in a subdirectory,
src/lib/profile/Makefile.am:73: but option 'subdir-objects' is disabled
...

Btw, you don't need to force-push and squash commits like this.  It's
fine (ie better) for the branch to maintain the history for large
feature branches like this.

Arg, I'll push a fix soon, just need to run it through the tests first.
Alternatively, merge #199 first.

Superseded by #290.


Resized container height is reset after refresh

Container height should be saved in local storage

Is there a way to set the default size of the window? It takes up way to much space.

You can add styles to the panelProps object.
Something like this. <ReactQueryDevtools panelProps={{ style: { height: '300px' } }} />

Fixed in v3

Fixed in v3


fix: remove hardcoded minikube version from build_local.sh

This change supports OLM minikube users locally since the currently hardcoded kubernetes version v1.16.4 is severely outdated and doesn't work on recent versions of minikube. The script will instead use the version of kubernetes associated with the existing version of minikube.
OLM has largely moved to kind for CI and local testing, but users running minikube locally should also be able to run OLM.
Signed-off-by: Daniel Sover<EMAIL_ADDRESS>
Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive

/lgtm

/lgtm


Add RangeExpressionContains to the standard PredicateCodableConfiguration

It looks like we missed an expression type in the standard configuration. This adds it to allow for encoding/decoding with predicates that contain these expressions without requiring it to be manually allowed.
Resolves #344

@swift-ci please test


Replace service address

Signed-off-by: aisuko<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Replace the service address and fixing the misspelling.
Signed commits

[x] Yes, I signed my commits.

https://github.com/meshery/meshery-istio/pull/341 Please hold on until we get confirm the test cases can cover the change.


Emitt events to Vue root instead locally

@randallknutson I have a suggestion (I can make a PR if you consider it worthwhile).
I think that it would be better to emit events to the Vue root instead in scope of local component like it is done now (here: https://github.com/formio/vue-formio/blob/v3.0.0/src/components/Form.ts#L131 and here: https://github.com/formio/vue-formio/blob/v3.0.0/src/components/Form.ts#L135 ). It takes away one issue I had with setting up listeners. Because Formio loads itself asynchronously I need to make sure that my refs are already available, sadly I had problems to grab my refs in "mounted" lifecycle hook, which made it problematic to attach my listeners. Now, if the event would have been emitted to the Vue root I could setup my listeners in whatever lifecycle hook I want and execute some callbacks involving having refs safely.

@randallknutson
Actually the one on instance should be left for compatibility, I would only add one on vue root. If I had permissions I would open the PR...

The problem I see defining it at the root level is when you have multiple forms instances.
What you should do is use existing events (as for example render) and create your logic from there.
For example:
@/components/FormioForm.vue
<template>
  <formio src="https://examples.form.io/example" @render="onFormRender"></formio>
</template>

<script>
import { Form } from 'vue-formio';

export default {
  name: 'formio-form',
  components: { formio: Form },
  methods: {
    onFormRender() {
      this.$root.$emit('my-root-event');
    },
  }
};
</script>

Now instead of using the vanilla vue-formio Form component you use yours.

@airarrazaval as you can see in my PR I actually changed my mind a bit and added the root level emit alongside component level emit. This way you can choose if you listen directly on component or on the $root.
So you can listen to any event emitted by any formio instance embedded in your component, no matter how deeply nested inside your component it is.
Still, thanks for giving me another idea on how to attach listener in a way that it ensures having reference to formio via $refs.
Anyway I guess I can close this one as I managed without it after all.


AWS Invoicing update

Coordinate with Vicky and AWS.

We are still waiting for the response from AWS as to what they suggest we do about their name change from AWS to AWS Canada. We are not the only customer for who the name change created big issues so AWS is trying to figure out a solution that would work for everyone.


fc when refresh tap

hi i ve implemented muzei support in my wallpapers app but in muzei when tap in setting refresh it fc, can you help me ?

__LIB_BP


Feature request: Asynchronous function callback

So what I am needing and I have been unable to figure out with the twig source is to allow for:
Twig.extendFunction("DatabaseCall", function (arguments) {
    return 'Template Stuff';
});

The problem is that node wants to do everything via callbacks... So what would be neat is to extend twig using a function that upon completion it does not continue rendering but instead waits for a callback... So like this...
Twig.extendFunctionAsync("Import", function (callback, name, twigVars) {
    // Pull database things
    Callback(ReturnVariable);
});

The exact problem I am having is I want to allow template creators to render items from the database using that function but to pull from the database it needs to be Async because node cannot do network calls synchronously.
I will keep plugging away at this but you guys have more insight as to how your renderer works...
Thanks for reading 👍

So I think what you're trying to do is probably similar to: https://github.com/twigjs/twig.js/issues/61, is that right?

I did not see that one. That is what I am intending to do because of the nature of a mysql call in node js.

Its definitely a cool idea, but unfortunately I really can't prioritize it at the moment because its not something you can do in Twig PHP. I'm currently aiming to try and get more compatibility with Twig PHP as my priority.

Makes sense. I am thinking of maybe rendering the template and using a randomized token as a placeholder for the variable then after the render is done going though and replacing the tokens with the returned variables. So kinda like a double render or a basic .replace('DBVAR','info') kind of thing.

Why it not work with {% for %} tag?
Simple example:
Function:
Twig.extendFunction('async_test', (id) => {
    return Promise.resolve(`Test: ${ id }`);
});

Template:

    {{ async_test(1000) }}

// ids is [2000, 20001, 20002]

    {% for id in ids  %}

            {{ async_test(id) }}

    {% endfor %}

returns

    Test: 1000

where #each is empty.
How i can fix it?

Duplicate of #61.


Refactor thermo_state

This PR refactors thermo_state! so that we can more easily move set_thermo_state_peq! logic into thermo_state!.
This is a step towards #949.

bors r+

bors r+


[Dialog] Content with scroll overlap

Describe the bug
When the content causes the scroll to show up, it applies to the whole dialog, instead to only the content, as the guidelines say. This leads to an overlap with the close action. Right now it displays like this:

This is how it should look like according to the guidelines:

I think @aweell can give us a lot of guidance on this issue as it is very much related to the guidelines. In this case I detect two problems:

The positioning of the close button is not correct and it is not the size indicated in the design guidelines. Even so, the size of 20x20 pixels indicated makes the button look very small.
The component does not control the content it receives, so the title is included in the scroll area.

I think we should review this component in depth.

I'll review it.
@marcialfps maybe we should contemplate having a title area predefined in the component so it's outside of the custom content area and never scrolls?
https://github.com/dxc-technology/halstack-style-guide/issues/238#issue-910200202

Regarding this issue, i think we have to reach an agreement. I understand what you say @aweell but by doing so, don't you think we lose flexibilty? since beforehand, we can't predict what is inside the Dialog component and which parts of that content are going to be scrollable. I think that decision has to be made by the user itself, not by us.
I agree maybe it is interesting to give a predefined dialog, but also to give the freedom to put inside whatever the user wants.

By having predefined sections on a dialog the user can always decide which ones to use, if I don't want to have a header I can remove that section and use only content and footer or even only content.
The current guidelines are actually exploring the idea of having this approach:

Right now we're providing a lot of flexibility so users can always change the padding-top or the overall padding to avoid the scroll and the close button overlap.
We can open a different discussion about if a dialog should be used for an amount of content that is going to produce overflow instead of just putting this content on a page.

Image extracted from the article: Modal vs Page: A Decision Making Framework by Ryan Neufeld
My conclusion here is that reviewing the component now will lead to some structural changes that will affect the current properties. The guidelines can be updated eluding the example of scrollable content since is something the user should avoid.

Closed via https://github.com/dxc-technology/halstack-style-guide/issues/238
@marcialfps the icon to be used for the close button:
https://fonts.gstatic.com/s/i/materialiconsoutlined/close/v15/24px.svg


Escape spaces in jr: media URLs

Supports enketo-express#218

Escapes jr: media URLs in the XML model transform
HTML src and href attributes were already escaped, but this adds test coverage

HTML src and href attributes were already escaped, but this adds test coverage

What cases in the test form were already being escaped?
I know you considered changes in Express or Transformer — what made you go in this direction?

What cases in the test form were already being escaped?

All of the cases except the final model check passed, because it was unescaped.

I know you considered changes in Express or Transformer — what made you go in this direction?

This is part of the direction we discussed on Slack, there will be corresponding changes to Express. This unifies the behavior so downstream users won’t need to handle the discrepancy between HTML/XML behavior.
Although technically this will cause upload defaults to exhibit the same failure mode as image labels, so it’s technically a breaking change. I think it’s a reasonable one for Express, as it’s correcting previously invalid URLs. But we’ll need to communicate that to other users and version appropriately (do we use semver?).
Apart from our discussion on direction, this felt like the right direction because

It provides consistent behavior that’s not environment-specific (URL should behave the same way in a browser environment if we go that direction)
It ensures the URLs produced are valid, which means they can also be used consistently in any environment.

Oh, it’s probably worth exposing the specific escape function so users, including Express, can use it too. Which would also allow more focused unit tests (though I think it’s good to keep the bug-related test for regressions).

Some notes as I try to make sense of all this.

cause upload defaults to exhibit the same failure mode as image labels

I think what you're saying is that currently express handles unescaped URLs correctly in the image label and default cases. The change here results in both image label and default cases being escaped meaning filenames with spaces in both cases will be broken in the same way in express?
As far as I understand it, this change affects only binary defaults. Here are some input binary defaults and outputs before and after the change:

Source
Before
After

jr://images/foo.png
jr://images/foo.png
jr://images/foo.png

jr://images/foo bar.png
jr://images/foo bar.png
jr://images/foo%20bar.png

jr://images/foo/bar.png
jr://images/foo/bar.png
jr://images/foo/bar.png

jr://images/hallo spaceboy/under pressure.png
jr://images/hallo%20spaceboy/under%20pressure.png

That all seems good. The test is misleading because it seems to imply that the jr://images scheme will be stripped.
Here are some input label images and outputs before and after the change:

Source
Before
After

jr://images/hallo.jpg
jr://images/hallo.jpg
jr://images/hallo.jpg

jr://images/foo bar.jpg
jr://images/foo%20bar.jpg
jr://images/foo%20bar.jpg

jr://images/foo/bar.jpg
jr://images/foo/bar.jpg
jr://images/foo/bar.jpg

jr://images/hallo spaceboy/spiders from mars.jpg
hallo%20spaceboy/spiders%20from%20mars.jpg
hallo%20spaceboy/spiders%20from%20mars.jpg

Nothing has changed which makes sense but I'd like to understand the choice of a case with a subpath. The jr://images scheme is stripped and I don't think it should be. As far as I know, it's not possible with any server so not really that important. But this makes the test cases look misleading.
Even stranger, the stripping seems to happen for jr://audio but not jr://video. This is aside from the issue at hand but again, I think it's important that the tests correctly reflect that the scheme should be passed on, not stripped.


Warning on sha :no_check?

I get a little nervous whenever I am unable verify the software I download. This is mitigated somewhat by the presence of SHA sums in most cask definitions; at least I know I am getting the same versions of apps you are seeing. But many casks have no checksums at all.
I understand there are reasons for this; e.g. Calibre, with unversioned downloads and frequent updates, would break a lot if you tried to enforce checksums. Maybe there is a potential solution here somewhere, but I imagine that any solution would require significant manual effort, which is a burden I don't want to place on anyone.
What would be nice though would be if I could get a warning when I attempt to install a cask without a checksum (and over insecure http). Or maybe you could manually check signatures of apps with spctl --assess, though that might possibly be more pain than it's worth. I'm fine if these are optional and not enabled by default, but it would be nice if there were some option for folks who are security conscious.

Fixed in https://github.com/caskroom/homebrew-cask/issues/16042


chif install windows 10power shellbelow problem

im install chef server created to chef url and also download kit key folder

Hi Anil, to work chef commands you should install ChefDK in your Workstation.
Please install chef DK from below URL and check.
https://downloads.chef.io/chefdk/

please read the official chef documentation for bootstrap the windows node because you have to install chef client manually on windows node and enable so configuration.

first in first open powershell as run as adminitrator and then install chef dk on your windows 10
once you installed then close the powershell and reopen.


Helm 3 alpha1: chart list replaces _ with :

Output of helm version:
version.BuildInfo{Version:"v3.0.0-alpha.1", GitCommit:"b9a54967f838723fe241172a6b94d18caf8bcdca", GitTreeState:"clean"}
When testing the new chart push/pull feature, I noticed that helm chart list will render incorrect ref values:
helm chart pull us.icr.io/my_registry/mychart:latest
latest: Pulling from us.icr.io/my_registry/mychart
Name: mychart
Version: 1.0.8
Meta: sha256:32e5dd94fcba61d0bc36664fc0f9e908e39552507f7694c21f7a34f19eb82572
Content: sha256:5282241bf2a576f84ab38c681cf325ad6f03d35100f76bfb31be119d86f9d675
Status: Chart is up to date for us.icr.io/my_registry/mychart:latest

helm3 chart list
REF                                       	NAME  	VERSION	DIGEST 	SIZE   	CREATED
us.icr.io/my:registry/mychart:latest	mychart	1.0.8  	5282241	3.1 KiB	26 minutes

Note the underscore in the registry path has been replaced with a :. It seems like all other helm chart commands recognise the original ref, so I think this is just a rendering issue with chart list.

@jdolitsky can you confirm if this has been fixed in more recent versions?

@bacongobbler yes, this substitution has been removed! closing


2h22 win10 pro 2H22

I would like to ask about the current computer using the 2H22 version of Windows 10 pro but it has been unable to connect multiple people. I would like to ask what the problem is?

Duplicate of https://github.com/stascorp/rdpwrap/issues/2359


How to hide a vertical guide line on a bar chart?

First of all, thank you for the library.
I want to hide vertical guide line in bar chart.
help will be appreciated.
Thanks

@anismansuri @i-schuetz  Any update in this?

To hide the guidelines, you have to pass ChartGuideLinesLayerAxis.x to the guidelines layer. To hide the axis line, you have to pass 0 as stroke width to the axis model, using this setting.

@i-schuetz Thanks !!  I am able to hide the vertical guide lines using ChartGuideLinesLayerAxis.x. But not able to set the stroke color only for one axis. As both of them are using the same axisStrokeWidth. How can I change only for Y axis?
let coordsSpace = ChartCoordsSpaceLeftBottomSingleAxis(chartSettings: chartSettings, chartFrame: frame, xModel: xModel, yModel: yModel)
let (xAxisLayer, yAxisLayer, innerFrame) = (coordsSpace.xAxisLayer, coordsSpace.yAxisLayer, coordsSpace.chartInnerFrame)

You're welcome! Please read my comment again. I edited it shortly after I posted it.

@i-schuetz  Thanks a lot buddy. 👍  it is working fine.


Process Asset File Extensions With Multiple Dots

Fixes #1276.
Not sure if this is how we want it or not, but this implements my suggestion for #1276. Totally open to suggestions on better ways to do this.

This might produce surprising results when using filenames containing periods, e.g. some-asset-1.2.png (not that I condone that sort of thing)
Seems like we might want to check .png first, then 2.png and finally 1.2.png and return the first error unless we do find a loader.

This might produce surprising results when using filenames containing periods, e.g. some-asset-1.2.png (not that I condone that sort of thing)
Seems like we might want to check .png first, then 2.png and finally 1.2.png and return the first error unless we do find a loader.

@bjorn3 and @rparrett, just pushed a commit that should address both of your notes.

@bjorn3 and @rparrett, just pushed a commit that should address both of your notes.

Oops, I think my original comment may have been slightly nonsensical.
I've been playing around with this as well as a learning exercise. I ended up adding some tests in my branch that might be useful.
https://github.com/rparrett/bevy/blob/multiple-dots/crates/bevy_asset/src/asset_server.rs

Oops, I think my original comment may have been slightly nonsensical.
I've been playing around with this as well as a learning exercise. I ended up adding some tests in my branch that might be useful.
https://github.com/rparrett/bevy/blob/multiple-dots/crates/bevy_asset/src/asset_server.rs

Oh, well, actually, I noticed that my example doesn't handle the test.1.character.yml case. :thinking: Did your version end up working, it might be better than mine. If it works, you could just submit a PR to replace this one. You've got tests too, which is good! :smile:

Oh, well, actually, I noticed that my example doesn't handle the test.1.character.yml case. :thinking: Did your version end up working, it might be better than mine. If it works, you could just submit a PR to replace this one. You've got tests too, which is good! :smile:

Did your version end up working

I'm not sure! I haven't tested it at all beyond those simple unit tests. I'm not sure if my implementation is good and free of side effects. I'm a total newbie at error juggling in rust.

Did your version end up working

I'm not sure! I haven't tested it at all beyond those simple unit tests. I'm not sure if my implementation is good and free of side effects. I'm a total newbie at error juggling in rust.

There, I made a combined updated version incorporating all of your feedback and my updates.

There, I made a combined updated version incorporating all of your feedback and my updates.

Before merging we should probably double check with @kabergstrom to make sure that atelier can support this scenario.

Before merging we should probably double check with @kabergstrom to make sure that atelier can support this scenario.

Address the review points. Also, I just stole @rparrett 's tests for this PR and @bjorn3 's implementation for the extension matching. All I did was the error formatter. :shrug: if you guys want to make commits that I can merge them into this PR so you get your names on it let me know.

Address the review points. Also, I just stole @rparrett 's tests for this PR and @bjorn3 's implementation for the extension matching. All I did was the error formatter. :shrug: if you guys want to make commits that I can merge them into this PR so you get your names on it let me know.

Don't sell yourself short! Documenting an issue, submitting a solution and wrangling a bunch of reviews and ad-hoc contributions is heroic effort in my book.

Don't sell yourself short! Documenting an issue, submitting a solution and wrangling a bunch of reviews and ad-hoc contributions is heroic effort in my book.

As far as I can tell, atelier-assets also can't do this, but it seems like it might be easy enough to add.
This chunk of code seems like the place to look.
https://github.com/amethyst/atelier-assets/blob/master/daemon/src/daemon.rs#L32

As far as I can tell, atelier-assets also can't do this, but it seems like it might be easy enough to add.
This chunk of code seems like the place to look.
https://github.com/amethyst/atelier-assets/blob/master/daemon/src/daemon.rs#L32

@rparrett good find. That looks like almost exactly what we are doing here in Bevy, so it should be just as simple to update there as it was here. :+1:

@rparrett good find. That looks like almost exactly what we are doing here in Bevy, so it should be just as simple to update there as it was here. :+1:

Cool. So I guess the biggest question is "would @kabergstrom accept the change", which we should answer before merging.

Cool. So I guess the biggest question is "would @kabergstrom accept the change", which we should answer before merging.

I like it! 😊👍

I like it! 😊👍

Cool! I just pushed an update resolving the merge conflicts.

Cool! I just pushed an update resolving the merge conflicts.


Increase aXe usage in Karma tests

Task Description

Since #4778 we have a custom toHaveNoViolations() matcher in our Karma test suite to verify that a given node/tree doesn't have any obvious a11y violations.
However, it isn't actually being used at the moment since I never really announced it anywhere.
Now the question is how it can be best used in our code base to be of most use.
For comparison, in the e2e test suite we run a similar check for the whole page in an afterEach call.
Is that feasible for Karma as well?
Or should we just try to use this matcher manually in some places that we think it's useful in?

pinging @BrittanyIRL @barklund @choumx for thoughts

Thoughts about trying it on new features that are getting tests written as we go? The first one that comes to mind is trying it out with the quick action menus tests that are getting written as we flesh the menus out. This would ideally make testing easier as axe should hopefully catch any poor a11y set up there.

Sounds like a good first step 👍

We've got bandwidth in pea pod  - will take this and add more a11y checks throughout codebase. possibly multiple PRs depending on what needs fixing.

Tests are added everywhere that makes sense in the editor, it should be easy to add as we go moving forward with new features.


Add video support

We want a user to include video's using shortcodes (for example for Youtube or Vimeo)

Added in v1.9.0


Bad diagnostic

public trait CollectionCore {}

public trait Collection: CollectionCore {

  type SliceCore: CollectionCore
  subscript slice(_ start: Int, _ end: Int): SliceCore { let }

}

extension Collection {

  subscript(_ start: Int, _ end: Int): SliceCore {
    yield Slice<Self>(core: self.slice[start, end]) // <=== Actual problem is here.
  }
}

type Slice<Base: Collection> {

  var core: SliceCore

  memberwise init

  typealias SliceCore = Base.SliceCore // error: type 'Base' has no member 'SliceCore'
}

@dabrahams would you have a suggestion? Otherwise please assign this to issue to yourself, since it is not very actionable.

Report a problem on the indicated line instead of telling me my type doesn't have a member that it clearly does have?

Then it's not a bad diagnostic problem. The problem in your extension is preventing name resolution to do its job. It's a bug.

It's a bug that results in a bad diagnostic; I'm not in a position to root-cause these things, but if you want to change the title of the issue to describe the problem better, please do.

This bug seems fixed. When I compile it now it points to the line that @dabrahams commented with "Actual problem is here."
Examples/test2.hylo:13.11-52: error: incompatible types 'Self.SliceCore' and 'Slice<Self>'
    yield Slice<Self>(core: self.slice[start, end]) // <=== Actual problem is here.
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I think this issue can be closed.

It seems fixed indeed (though one will have to add appropriate access modifiers to now that they are enforced).
I can't really tell what @dabrahams was expecting so he should be the one telling whether we have to keep this issue open or not.

I was expecting the message that "Base has no member SliceCore" to not be reported on the 2nd to last line and for a diagnostic to be reported on the line with the arrow.  If both those expectations are now met, you can close it.


adaptive concurrency: Filter configuration and integration tests

This patch brings the concurrency controller and the adaptive concurrency control (ACC) filter together to make the filter fully useable with integration tests.
The integration tests make use of the fault filter, placed after the ACC filter, to emulate request latencies and to also move time forward. Even though this is against the recommendation in the documentation to have the filter come before all other filters, it was necessary to have last. Not every request makes it to the upstream due to occasionally being blocked by the ACC filter, so it was not possible to simply call timeSystem().sleep and rely on the autonomous upstream to reply to the requests.
Patch 3/n towards #7789.
Temporal behavior
Now that all the pieces are together, it's worth comparing the filter's behavior with what we expecte from the proof-of-concept. Time sampled stats show similar behavior to the proof-of-concept filter's data in #7789. Here's a plot of latencies without the adaptive concurrency filter:

Now with the adaptive concurrency filter:

/wait

Marking as ready since the CI release test just flaked out. The thread_local_store_test works fine for me locally when tested on release:
INFO: Elapsed time: 282.725s, Critical Path: 152.57s
INFO: 1329 processes: 1329 linux-sandbox.
INFO: Build completed successfully, 1687 total actions
//test/common/stats:thread_local_store_test                              PASSED in 27.3s

Executed 1 out of 1 test: 1 test passes.
INFO: Build completed successfully, 1687 total actions

tallen@legion ~/src/envoy [acc_2]
± % git log | head -1                                                                                !10376
commit 6f5684661ddcdba6cc38f6f42fbcaef8da3ea149 (HEAD -> acc_2, tony/acc_2)

/wait

@jmarantz Matt suggested I run this testing approach by you if that's alright. I'm having some trouble using simulated time to achieve what I want here without introducing delays in an autonomous upstream and hitting the "only_one_thread.h" assertions.
In these tests, I'm trying to send multiple requests through the adaptive concurrency filter, but I don't want the upstream to reply to any requests until all requests in that batch have been sent. Some of these requests will be blocked by the filter, so they won't make it to the upstream. I was able to hack something together in this PR, but it doesn't seem to work for one specific test, where it hangs while sending the 2nd outstanding request.
The relevant code for sending requests in my test can be found here.  After the requests are all sent, I'm making the upstream reply to some subset of the requests via calls to this function with expect_forwarded set to true.
This seems to work fine for the first two tests, but the one I disabled seems to hang on waitForHttpConnection while sending the second request in the batch.
Do you have any thoughts on this or suggestions for a different approach?

/retest

First of all this stuff looks really cool and happy to help if I can.
Hopefully simulated time can help; I'll try to dig in later tonight when I get the chance.

I looked briefly at the test and wanted to see if I can suggest a methodology where we always advance time only from the main testing thread.
And by 'advance time' here I mean anything that blocks forward progress waiting for time to advance. This can be in the form of a timeSystem().sleep() or a waitFor of any flavor. I think things will work best and be easiest to reason about if it's only the test thread that does this.
All other threads that want to block on an event, IMO, should do so via timer callbacks or blocking on condition variables that are set from other threads.
At first glance your test does appear to follow this but then I wouldn't expect only_one_thread.h assertions. Can you describe more about what your test threads are doing to trigger those assertions?

Ah sorry, we have a misunderstanding. This current patch is not hitting the only_one_thread.h assertions. My previous attempt at writing this integration test ran into the assertions because I was attempting to advance time in the autonomous upstream. To avoid confusion, let's just disregard my previous comment on the assertion. I'll just provide some more detail on what I'm hoping to achieve now and the problems I'm running into. Apologies if I'm rehashing the previous post.
The adaptive concurrency filter will let through some number of requests equal to the concurrency limit before sending local replies to any requests beyond that limit. So let's say I have a concurrency limit of 5 and I send 10 requests to the integration test framework's fake upstream. I'd expect the first 5 requests to leave the codec_client and make it through the filter to the upstream and the last 5 requests to get 503'd by the filter and never make it to the fake upstream. In these integration tests, I essentially want to stall the requests that make it through to the upstream until every request is sent and acted on by the adaptive concurrency filter. I'd then have the fake upstream reply to all of the requests sent to it.
The issue is with one of the integration tests that I have disabled now. Its behavior boils down to a loop that sends a request and waits for a response from the upstream. It uses the same functions as the other two tests, but for some reason I can't explain, it hangs on the second call to waitForHttpConnection. The test does not exhibit this behavior if I use an autonomous upstream and don't use simulated time.
I spoke with Matt about this behavior the other day and he suggested I run this patch by you to hear your thoughts on whether my approach is misguided and whether I'm using the fake upstream correctly. The requirements for my test are a bit different than all of the other integration tests, due to the need for stalling requests at the upstream.
Let me know if I can shed some more light on anything.

can you point to the api for this Pr please?

@jmarantz if this event-driven testing approach were in place, these tests would be a breeze! I've spent a lot of time spinning my wheels on this, so I'm tempted to revisit this after  SimulatedTimeSystemHelper::waitFor* is ripped out. I really want to put in some more complex integration tests for this filter, so I might look into doing this on the side.
Regarding the problems with the disabled tests- no tests in the current iteration of this patch are hitting the only_one_thread.h assertions. I was referring to a previous attempt at achieving the request buffering at the upstream.
The problem now is that the last test, DISABLED_TestConcurrencyLimitEnforced, is getting stuck here when waiting for the 2nd HTTP connection. Debugger shows consumed_connections_ is non-empty , but the upstream is stuck waiting on something to show up in new_connections_ after the client has already sent a new request.
The request/response pattern of this test doesn't deviate from the others which do not seem to have any issues running.
Also, simulated time causes both disabled tests to take ~2.5x longer to execute on my desktop and was resulting in MacOS CI to timeout. I'm having a lot of issues with these tests!
@mattklein123 do you think we should leave the tests disabled until I or someone else get around to changing the waitFor* API in the integration test infrastructure?

@mattklein123 do you think we should leave the tests disabled until I or someone else get around to changing the waitFor* API in the integration test infrastructure?

Let's just trim down the PR to a set of integration tests that work (even if super simple) with a bunch of TODOs around things that you want to add later and we can track them in follow ups?
/wait

@mattklein123 in that case the PR is ready to go. The flakey tests are disabled with TODOs in the comments.

@tonya11en sorry I meant actually delete the tests for now and leave TODOs of further tests to write. I would rather just focus on what is working. Thank you!

/wait

Please merge master. (Might as well fix the nits that I pointed out at the same time since you have to push again.)
/wait

Not recently- let me go ahead and kick off 1000 and report back before merge.

@mattklein123 looks stable:
>> btd //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test --runs_per_test=1000 --test_timeout=20 --jobs=1
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/home/tallen/src/envoy/tools/bazel.rc
INFO: Invocation ID: 457c1652-a84a-4ea4-8ef9-fd8f885fee03
INFO: Analyzed target //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test (0 packages loaded, 0 targets configured).
INFO: Found 1 test target...
Target //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test up-to-date:
  bazel-bin/test/extensions/filters/http/adaptive_concurrency/adaptive_concurrency_integration_test
INFO: Elapsed time: 1428.001s, Critical Path: 1.56s
INFO: 1000 processes: 1000 linux-sandbox.
INFO: Build completed successfully, 1001 total actions
//test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test PASSED in 1.5s
  Stats over 1000 runs: max = 1.5s, min = 1.3s, avg = 1.4s, dev = 0.0s

Executed 1 out of 1 test: 1 test passes.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see whINFO: Build completed successfully, 1001 total actions

I needed to make sure there weren't multiple copies of this integration test running at the same time. When running it with 12 concurrency workers, there was a 2% failure rate, but from my investigations, I think this was due to the integration test framework and the fake upstreams.

I needed to make sure there weren't multiple copies of this integration test running at the same time. When running it with 12 concurrency workers, there was a 2% failure rate, but from my investigations, I think this was due to the integration test framework and the fake upstreams.

This means it will definitely flake in CI. It should work 100% of the time with concurrent workers, so we will need to investigate this unfortunately.
/wait

Alright, now we're cooking:
>> btd //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test --runs_per_test=1000 --test_timeout=20
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/home/tallen/src/envoy/tools/bazel.rc
INFO: Invocation ID: e2f638f0-7bf8-4082-bf2e-0fa2655362c9
INFO: Build options --cache_test_results, --run_under, --runs_per_test, and 1 more have changed, discarding analysis cache.
INFO: Analyzed target //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test (0 packages loaded, 14062 targets configured).
INFO: Found 1 test target...
Target //test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test up-to-date:
  bazel-bin/test/extensions/filters/http/adaptive_concurrency/adaptive_concurrency_integration_test
INFO: Elapsed time: 127.585s, Critical Path: 1.79s
INFO: 1000 processes: 1000 linux-sandbox.
INFO: Build completed successfully, 1001 total actions
//test/extensions/filters/http/adaptive_concurrency:adaptive_concurrency_integration_test PASSED in 1.8s
  Stats over 1000 runs: max = 1.8s, min = 1.3s, avg = 1.5s, dev = 0.1s

Executed 1 out of 1 test: 1 test passes.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see whINFO: Build completed successfully, 1001 total actions

12 concurrent jobs this time.
There were actually 2 races that needed to be fixed:

The adaptive concurrency filter was responding to requests that it was rejecting before the test was able to send the request data. This caused the integration test's codec client to use a bogus stream and segfault. This was fixed by just sending header-only requests.
The header-only requests were then sent so quickly that the counters were non-deterministic. This required us to wait for the blocked counter to be incremented after each request before proceeding. Now the stats are as we'd expect.


2142_dcount_parameter

Changelog category (leave one):

Bug Fix (user-visible misbehavior in official stable or prestable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

Done


Add close button to tag modal

What is the motivation for adding/enhancing this feature?

The "add tag" modal doesn't have a dedicated button for closing it which makes it confusing for the user when they are don't selecting their tags and want to exit the screen. Adding screenshot for proposed UI of closing modal.

@dt2patel sir, a close button is there in the 'include tags' modal already, do we need to make any other changes?

@k2maan a close button doesn't communicate to the user that their changes will be saved


GUVNOR-2173 - Asset Oracle: Change Impact prediction

Change Impact, Part I: building a reference infrastructure that we can query.
For an explanation of the changes, see https://github.com/droolsjbpm/kie-wb-common/pull/414
PR set:

https://github.com/uberfire/uberfire/pull/455
https://github.com/droolsjbpm/kie-wb-common/pull/414
https://github.com/droolsjbpm/drools-wb/pull/257
https://github.com/droolsjbpm/jbpm-designer/pull/375
https://github.com/droolsjbpm/jbpm-form-modeler/pull/63

Also, this PR depends on https://github.com/droolsjbpm/jbpm/pull/511

@tsurdilo  Would you mind also reviewing this? Thanks! It will help to read droolsjbpm/kie-wb-common#414 first.

Fixed missing licenses.

jenkins retest this

@mrietveld could i pls have couple days to test this locally to make sure there is no impact on ui? im in middle of bigger pr now so pls give me just couple days or if @jlindop has some time now he can test as well. thanks.

@tsurdilo no problem.

jenkins retest this
(really fixed the non-public method/errai marshalling problems.. )

@mrietveld This is still red.

Mr. Jenkins, the please of the retest would be green. Yes. ;)

There was once a Jenkins that ate tests. "Please, may I have some more?" it would ask and then retest.

@mrietveld   This builds now, which is good, but I haven't been able to test it.
I've re-built all the repo's which still have unmerged commits for GUVNOR-2173 and built kie-wb-distributions/kie-wb, then deployed the wildfl10 war file to wildfly10. The war fails to start with this error:
16:17:16,835 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."kie-wb-7.0.0-SNAPSHOT-wildfly10.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-wb-7.0.0-SNAPSHOT-wildfly10.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DefinitionService with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject protected org.jbpm.designer.server.indexing.BPMN2FileIndexer.bpmn2Service
at org.jbpm.designer.server.indexing.BPMN2FileIndexer.bpmn2Service(BPMN2FileIndexer.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)

16:17:16,844 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie-wb-7.0.0-SNAPSHOT-wildfly10.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."kie-wb-7.0.0-SNAPSHOT-wildfly10.war".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-wb-7.0.0-SNAPSHOT-wildfly10.war".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type DefinitionService with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject protected org.jbpm.designer.server.indexing.BPMN2FileIndexer.bpmn2Service
at org.jbpm.designer.server.indexing.BPMN2FileIndexer.bpmn2Service(BPMN2FileIndexer.java:0)
"}}

@jlindop Thanks, looking into it.

@jlindop Fixed. The problem was that the jbpm-services-cdi module, which produces the DefinitionService CDI impl, was not included in either jbpm-designer-standalone or the workbench.

Argh.. fixing. jbpm-kie-services includes dashbuilder jars, which mess up the build..

@jlindop Argh, needs another PR to fix this.

@cristianonicolai as I will be off for a couple of days, can you merge this PR series once this one as a plus one and is green? Thanks.

@csadilek will do ;)

@jomarko @tsurdilo  Will one of you test this when it's ready to test (Marco's working on it)? See above for the set of dependent PR's. I'm on PTO next week, and @mrietveld  is leaving on Aug31st, so we should try to merge it as soon as we can. Thanks, Jeremy.

@jlindop I can't promise, but if I will have a moment I can try it. I will contact @tsurdilo when the PR will be ready and I will be out of time.

@jomarko @tsurdilo (and @mswiderski ?). This is done. If you have any questions, please let me know.
( @manstis Once this is done, the rest can be merged as well? )

looks very good to me - from the process information capturing point of view. Thanks @mrietveld for implementing the listener in designer. I do believe that is the cleanest solution even though it does duplicate tiny bit of code.

@jomarko or @tsurdilo, would either of you have some time to review this? I have 3 other PR's waiting on this.
Thanks!

Here are my comments:

DesignerProcessDataEventListener I did not find tests for this class and it seems to be as worth to be tested. Next there is typo error in variable functionImpot. It should be functionImpot. And the last question to this class. There is used is code StringUtils.isEmpty(). I looked at implementation of this and I think that it evaluates to false for cases like this StringUtils.isEmpty(' '). Is it fine?

DesignerFindDataTypesQuery and FindRuleFlowNamesQuery. In these classes I am wondering about methods toQuery() and validateTerms().

I think that in DesignerFindDataTypesQuery.toQuery(terms) is redundant check if terms are not null and empty.
Shouldn't be also in DesignerFindDataTypesQuery.validateTerms(terms) code that ensures that required term was found? Please compare DesignerFindDataTypesQuery.validateTerms(terms) with FindRuleFlowNamesQuery.validateTerms(terms) to see my point.

@jomarko Thanks!

Tests: the test for the DesignerProcessDataEventListener class is this class: BPMN2FileIndexerIndexingTest.
functionImpot: will fix
redundant check: I'll remove that
validateTerms: will fix

Thanks.

@mrietveld thanks, and the last thing. Is it fine if StringUtils.isEmpty(' ') evaluates to false in DesignerProcessDataEventListener?

@jomarko Yes, that's correct (it should evaluate to false and not to true!)

@jomarko Thanks for the feedback -- I've fixed the validateTerms and toQuery methods, and also added a test for the validateTerms method.
(The toQuery is tested in the indexing test).

jenkins please retest

+1


AMBARI-23092. Deleting a Group from the Group detail page navigates t…

…o the Cluster Information page
What changes were proposed in this pull request?
Deleting a Group from the Group detail page navigates to the Cluster Information page
How was this patch tested?
manually
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/838/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/990/
Test PASSed.


check if LibreSSL installed instead of OpenSSL

Hi,
Found an issue with 06-setup-certs.sh on MacOS with default LibreSSL as this does not support option -addext
Installing OpenSSL via Brew, and changing the PATH resolved the issue.
This PR ensures that LibreSSL is not being used, and will fail (exit 1) should that be the case.
Regards,
Jon

#243 gets rid of openssl commands in favor of cert-manager.

@sudo-bmitch  What are the timelines for cert-manager?

Whenever the PR gets approved. Hopefully by next week.