Release next MariaDB4j version 2.4.0

There have been a number of contributions to MariaDB4j recently which warrant a new release.
https://github.com/vorburger/MariaDB4j/blob/master/CHANGES.md needs to be updated.
Version should be major 2.4.0 not minor 2.3.1 IMHO - thoughts, anyone?
#63 from @duttonw should still make it into this release; it's almost hthere.
#113 from @usmanakram232 I don't know - shall we wait?
#156 needs to solved so that I can release.

https://github.com/vorburger/MariaDB4j/pull/146 would be a good edition in the next release

#189

#207

https://github.com/vorburger/MariaDB4j/blob/master/CHANGES.md needs to be updated.

d4b95a6d13d72db70c62576dd4e9b7d8279412f8

Version should be major 2.4.0 not minor 2.3.1 IMHO - thoughts, anyone?

42cc6e42a25d84e3a7be10182f675fc7e02f6616 (in #212)

Just did the mvn release:perform -Pgpg for 2.4.0, it should show up on Maven central shortly; FTR:
(...)
    [INFO] --- maven-install-plugin:2.4:install (default-install) @ mariaDB4j-maven-plugin ---
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/pom.xml to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-javadoc.jar to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar.asc
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.pom.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom.asc
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc to /home/vorburger/.m2/repository/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc
    [INFO]
    [INFO] --- nexus-staging-maven-plugin:1.6.7:deploy (injected-nexus-deploy) @ mariaDB4j-maven-plugin ---
    [INFO] Performing local staging (local stagingDirectory="/home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging")...
    [INFO]  + Using server credentials "ossrh" from Maven settings.
    [INFO]  * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.14.11-01 and edition "Professional"
    [INFO]  * Using staging profile ID "12bb4759cb85ae" (matched by Nexus).
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.jar to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/pom.xml to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-javadoc.jar to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.jar.asc to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar.asc
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0.pom.asc to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom.asc
    [INFO] Installing /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc to /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/target/nexus-staging/staging/12bb4759cb85ae/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc
    [INFO] Performing remote staging...
    [INFO]
    [INFO]  * Remote staging into staging profile ID "12bb4759cb85ae"
    [INFO]  * Created staging repository with ID "chvorburger-1042".
    [INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042
    [INFO]  * Uploading locally staged artifacts to profile ch.vorburger
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar.asc (455 B at 637 B/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/maven-metadata.xml (324 B at 644 B/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-sources.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-sources.jar.asc (455 B at 3.1 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/maven-metadata.xml (322 B at 721 B/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.jar.asc (455 B at 6.1 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.jar (16 kB at 22 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.pom (2.6 kB at 4.9 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/maven-metadata.xml (311 B at 812 B/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.pom.asc (455 B at 5.2 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.jar (93 MB at 4.5 MB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.pom (2.1 kB at 7.9 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/maven-metadata.xml (315 B at 1.1 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.jar.asc (455 B at 7.2 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-javadoc.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-javadoc.jar (99 kB at 125 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/maven-metadata.xml (316 B at 1.1 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.pom.asc (455 B at 9.1 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom.asc (455 B at 6.0 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.jar (76 kB at 256 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0.pom (15 kB at 80 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/maven-metadata.xml (243 B at 916 B/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/2.4.0/mariaDB4j-pom-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/2.4.0/mariaDB4j-pom-2.4.0.pom.asc (455 B at 6.0 kB/s)
    Downloading from ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/maven-metadata.xml
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/maven-metadata.xml
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/maven-metadata.xml (315 B at 929 B/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0.jar.asc (455 B at 5.3 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0-sources.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0-sources.jar.asc (455 B at 5.8 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0-sources.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j/2.4.0/mariaDB4j-2.4.0-sources.jar (3.0 kB at 14 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-javadoc.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-javadoc.jar (25 kB at 92 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-sources.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-sources.jar.asc (455 B at 3.1 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.jar.asc (455 B at 5.5 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-sources.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-sources.jar.asc (455 B at 6.6 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-sources.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-sources.jar (4.4 kB at 21 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0.pom.asc (455 B at 6.7 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar (53 kB at 167 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.jar (41 kB at 151 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0.pom (2.1 kB at 7.9 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-maven-plugin/2.4.0/mariaDB4j-maven-plugin-2.4.0-javadoc.jar.asc (455 B at 7.2 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-javadoc.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-javadoc.jar (29 kB at 127 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-sources.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-sources.jar (21 kB at 77 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-javadoc.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-core/2.4.0/mariaDB4j-core-2.4.0-javadoc.jar.asc (455 B at 6.8 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-sources.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-sources.jar (4.7 kB at 22 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/2.4.0/mariaDB4j-pom-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-pom/2.4.0/mariaDB4j-pom-2.4.0.pom (5.4 kB at 26 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.pom.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.pom.asc (455 B at 6.0 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-javadoc.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-app/2.4.0/mariaDB4j-app-2.4.0-javadoc.jar.asc (455 B at 7.6 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-javadoc.jar.asc
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0-javadoc.jar.asc (455 B at 6.7 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.jar
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.jar (19 kB at 86 kB/s)
    Uploading to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.pom
    Uploaded to ossrh: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1042/ch/vorburger/mariaDB4j/mariaDB4j-springboot/2.4.0/mariaDB4j-springboot-2.4.0.pom (1.3 kB at 5.5 kB/s)
    [INFO]  * Upload of locally staged artifacts finished.
    [INFO]  * Closing staging repository with ID "chvorburger-1042".

    Waiting for operation to complete...
    ........

    [INFO] Remote staged 1 repositories, finished with success.
    [INFO] Remote staging repositories are being released...

    Waiting for operation to complete...
    .......

    [INFO] Remote staging repositories released.
    [INFO]
    [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ mariaDB4j-maven-plugin ---
    [INFO] Building jar: /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-sources.jar
    [INFO]
    [INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ mariaDB4j-maven-plugin >>>
    [INFO]
    [INFO] --- license-maven-plugin:1.17:check-file-header (default) @ mariaDB4j-maven-plugin ---
    [INFO] Will search files to update from root /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java
    [INFO] Will search files to update from root /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/test/java
    [INFO] Scan 7 files header done in 6.404ms.
    [INFO] All files are up-to-date.
    [INFO]
    [INFO] --- maven-checkstyle-plugin:3.0.0:check (validate) @ mariaDB4j-maven-plugin ---
    [INFO] Starting audit...
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/StartMojo.java:29: Wrong lexicographical order for 'java.io.IOException' import. Should be before 'org.apache.maven.plugins.annotations.ResolutionScope'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/StartMojo.java:57: 'if' child have incorrect indentation level 15, expected level should be 16. [Indentation]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:31: Wrong lexicographical order for 'java.io.File' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:32: Wrong lexicographical order for 'java.io.IOException' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:33: Wrong lexicographical order for 'java.nio.charset.Charset' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:34: Wrong lexicographical order for 'java.nio.charset.StandardCharsets' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:35: Wrong lexicographical order for 'java.nio.file.Files' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:36: Wrong lexicographical order for 'java.util.Arrays' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:37: Wrong lexicographical order for 'java.util.List' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:38: Wrong lexicographical order for 'java.util.Optional' import. Should be before 'org.apache.maven.project.MavenProject'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:92: First sentence of Javadoc is incomplete (period is missing) or not present. [SummaryJavadoc]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/AbstractRunMojo.java:98: First sentence of Javadoc is incomplete (period is missing) or not present. [SummaryJavadoc]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/src/main/java/ch/vorburger/mariadb4j/utils/DBSingleton.java:29: Empty line should be followed by <p> tag on the next line. [JavadocParagraph]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:15: Wrong lexicographical order for 'javax.xml.parsers.DocumentBuilder' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:16: Wrong lexicographical order for 'javax.xml.parsers.DocumentBuilderFactory' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:17: Wrong lexicographical order for 'javax.xml.parsers.ParserConfigurationException' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:18: Wrong lexicographical order for 'java.io.IOException' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:19: Wrong lexicographical order for 'java.io.InputStream' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:20: Wrong lexicographical order for 'java.util.ArrayList' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:21: Wrong lexicographical order for 'java.util.List' import. Should be before 'org.xml.sax.SAXException'. [CustomImportOrder]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:31:1: '{' at column 1 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:68:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:72:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:77:9: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:79:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:81:9: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:83:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:85:9: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:87:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:89:9: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:91:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:93:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:95:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:97:17: '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:99:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:106: First sentence of Javadoc is incomplete (period is missing) or not present. [SummaryJavadoc]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:111:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:113:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:118:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:133:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:135:9: '}' at column 9 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:137:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:139:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:141:13: '}' at column 13 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:143:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:158:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:164:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:169:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:176:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:182:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:188:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:191:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:195:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:202:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:206:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:209:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:218:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:221:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:225:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:233:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:238:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:242:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:245:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:249:13: '}' at column 13 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:251:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:257:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:264:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:273:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:275: Distance between variable 'parameterDescription' declaration and its first usage is 5, but allowed 3.  Consider to make that variable as final if you still need to store its value in advance (before method calls that might do side effect on original value). [VariableDeclarationUsageDistance]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:279:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:280: 'if' child have incorrect indentation level 10, expected level should be 12. [Indentation]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:285:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:291:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:297:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:301:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:319:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:323:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:339:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:341:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:357:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:365:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:381:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:388:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:390:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:392:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:396:17: '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:398:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:404:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:407:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:409:17: '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:411:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:413:17: '}' at column 17 should be on the same line as the next part of a multi-block statement (one that directly contains multiple blocks: if/else-if/else or try/catch/finally). [RightCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:415:17: '{' at column 17 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:430:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:433:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:437:9: '{' at column 9 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:439:13: '{' at column 13 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:448:5: '{' at column 5 should be on the previous line. [LeftCurly]
    [WARN] /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/generated-sources/plugin/ch/vorburger/mariadb4j/HelpMojo.java:451:9: '{' at column 9 should be on the previous line. [LeftCurly]
    Audit done.
    [INFO]
    [INFO] --- maven-plugin-plugin:3.5.2:helpmojo (generated-helpmojo) @ mariaDB4j-maven-plugin ---
    [INFO] Using 'UTF-8' encoding to read mojo source files.
    [INFO] java-javadoc mojo extractor found 0 mojo descriptor.
    [INFO] java-annotations mojo extractor found 3 mojo descriptors.
    [INFO]
    [INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < generate-sources @ mariaDB4j-maven-plugin <<<
    [INFO]
    [INFO]
    [INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ mariaDB4j-maven-plugin ---
    [INFO] Building jar: /home/vorburger/dev/MariaDB4j/git/MariaDB4j/target/checkout/mariaDB4j-maven-plugin/target/mariaDB4j-maven-plugin-2.4.0-sources.jar
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] mariaDB4j-pom ...................................... SUCCESS [  4.171 s]
    [INFO] mariaDB4j-core ..................................... SUCCESS [  5.312 s]
    [INFO] mariaDB4j (all-in-one artifact) .................... SUCCESS [02:05 min]
    [INFO] mariaDB4j-springboot ............................... SUCCESS [ 18.610 s]
    [INFO] mariaDB4j-app ...................................... SUCCESS [ 12.992 s]
    [INFO] mariaDB4j-maven-plugin ............................. SUCCESS [02:24 min]
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 05:11 min
    [INFO] Finished at: 2019-02-12T03:07:20+01:00
    [INFO] Final Memory: 89M/1081M
    [INFO] ------------------------------------------------------------------------
    [WARNING] The requested profile "release" could not be activated because it does not exist.
[INFO] Cleaning up after release...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] mariaDB4j-pom ...................................... SUCCESS [06:13 min]
[INFO] mariaDB4j-core ..................................... SKIPPED
[INFO] mariaDB4j (all-in-one artifact) .................... SKIPPED
[INFO] mariaDB4j-springboot ............................... SKIPPED
[INFO] mariaDB4j-app ...................................... SKIPPED
[INFO] mariaDB4j-maven-plugin ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:14 min
[INFO] Finished at: 2019-02-12T03:07:21+01:00
[INFO] Final Memory: 25M/286M
[INFO] ------------------------------------------------------------------------

#213


display raw json of opaque fields in transaction view

display a limited form of the raw JSON (opaque fields) in the public view of the completed transaction view.

I don't think we should do this -- action views should either be complete, or not rendered at all ("Unimplemented Action"). We don't ever want to be exposing raw JSON or any other unformatted content in the transaction view components. They should have a semantically meaningful representation.


Do enabling windows auth for a website is required to make AD authentication work?

Not sure if this is an issue or just a question?  Yes you must enable windows authentication for the website if you want to use this extension.

It's a question, thanks.

I finally managed to make it work! 😌 I thought that Do Not Automatically Create Users? flag is about creating accounts in AD, but it is about creating corresponding accounts in DNN.
Enabling windows authentication in IIS is not required - at least if you do not need it to be transparent, I suppose.
Thanks for your work, @sawest! 👍


Fix remoteApps

The assert that have been removed were preventing RAIL from working when you have an intermediary screen before seeing the application.

+1


yew-macro: Make self-closing slash optional for void elements

Problem
Void Elements
From https://html.spec.whatwg.org/multipage/syntax.html#start-tags:

Then, if the element is one of the void elements, or if the element is a foreign element, then there may be a single U+002F SOLIDUS character (/). This character has no effect on void elements, but on foreign elements it marks the start tag as self-closing.

The "/" of <br/> is optional per the spec however Yew's html! macro requires it.
Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[x] I don't have time to fix this right now, but maybe later

From the specification you're linking, the void elements are the following:

Void elements
area, base, br, col, embed, hr, img, input, link, meta, param, source, track, wbr

Personally, I'm not a big fan of allowing this, because it looks to me that it's pure laziness that became standard. IMO implementing this would complicate the html! macro implementation. But I think that printing helpful error in the case of unclosed void elements could be a pragmatic and easy solution. What do you think @kellytk?

@totorigolo

Personally, I'm not a big fan of allowing this, because it looks to me that it's pure laziness that became standard.

As I understand it, XHTML was oriented toward XML and HTML5(tm) is oriented toward SGML, wherein subtle differences in void and element closing exist.  https://stackoverflow.com/a/3558200 is a primer.  Irrespective, questioning the spec is out of scope here at least for myself.
I don't know if the intent of the html! macro is to completely conform to the HTML spec.  I would defer to documentation or a comment by @jstarry.  If complete conformance is the intent, a fix should be implemented, otherwise whatever the intent of the macro is should guide how the issue is addressed.
A more helpful error message would be appreciated.

Agreed that we should at the very least not allow void elements to have children. We can compile time check this with the proc macro

Related: #1217


Ability to specify secret ownerReference as part of the Certificate request

Is your feature request related to a problem? Please describe.
We are running applications for a variety of customers in our clustered environment and want both the ability to have secrets automatically removed when the Certificate is deleted and want to keep them. Most of our use cases are probably because we're using Flux/GitOps for our deployment model. Use cases:

Feature-branch deployments that come and go, so want to have the secret removed when the branch is nuked
Sometimes, an entire application needs to be bounced, so teams are removing/re-adding the manifests. In these cases, we don't want to nuke the secrets

Describe the solution you'd like
I'd like to have the ability to specify on the Certificate itself whether the ownerReference for the secret should be set, rather than a global on or off.
Describe alternatives you've considered
We've looked at using the secretTemplate to set annotations on the secrets and then have a cleanup job nuke all secrets that no longer have an associated Certificate. But, it would be nice if we didn't have to develop this.
/kind feature

/remove-lifecycle stale

/remote-lifecycle stale

/remove-cycle stale

/remove-lifecycle stale

/remove-lifecycle rotten

/remove-lifecycle stale


Show how to use a custom policy in output caching

Fixes #27687
Internal review URL

ping @Rick-Anderson @sebastienros


resin local discovery requires running as sudo

As part of the discovery of local devices, we've needed to ensure that the implementation of MDNS we use listens/sends on every available NIC. Whilst our fix to MDNS (https://github.com/resin-io-modules/multicast-dns/tree/listen-on-all-interfaces) works fine when there's no other implementation of MDNS/DNS-SD running, it requires resin-cli to be run using sudo when there are other instances (as <IP_ADDRESS>:5353 needs to be shared). This is not ideal.
A solution to this is to actually hook into any underlying services that are already carrying out these duties:

Linux - avahi-daemon should it have been installed
OSX - mDNSResponder (the Bonjour implementation)
Windows - mDNSResponder, should it have been installed

A fallback for Linux/Windows is to rely on the current JS implementation.
A spec. needs writing for this, along with an implementation.

@flesler @afitzek Hi both, you've been potentially earmarked as chaps that could potentially pick this up and run with it. Would either of you like to take this on? ;-)
cc @shaunmulligan @alexandrosm

Hi @hedss, I'm currently working on the tableau integration and after that on the persistent api keys which should take some weeks. I could take it but will be on the queue for weeks

@flesler Might be better than nothing, dude. I guess it depends on how urgent Shaun and Alex think this is.

@hedss If this needs work sooner, I have a space in my planning once I've got the analytics & signup inbox work sorted, which is getting very very close to done already now. Start of next week at the latest.
Otoh I don't know much about MDNS, but I'm very happy to look into it, and the above all sounds very achievable.

@pimterry If you think you could, then that would be wonderful, thank you! I'll hopefully be able to answer any relevant questions about it, too.

An update on this: it's been bumped to second on my list by https://github.com/resin-io/resin-cli/issues/549, but it will be coming straight after that.

@pdcastro I think we should close either this or #1714 as duplicate, since they are the same issue.


Prevent unbound variable when running with no args

When running janet with no args you currently get:
> asdf plugin add janet https://github.com/jakski/asdf-janet.git
> asdf install janet latest
[snip]
> asdf global janet latest
> which janet
<asdf_install_dir>/shims/janet

> janet
<asdf_install_dir>/lib/commands/command-exec.bash: line 23: shim_args[@]: unbound variable

With these changes:
> asdf plugin add janet https://github.com/kiliantyler/asdf-janet.git
> asdf install janet latest
[snip]
> asdf global janet latest
> which janet
<asdf_install_dir>/shims/janet

> janet
Janet 1.35.2-meson macos/aarch64/clang - '(doc)' for help
repl:1:>

Ref:
https://github.com/code-lever/asdf-rust/issues/17
code-lever/asdf-rust@17a96bd (#19)

@kiliantyler Thank you for reporting this. Can you verify that the following solution https://github.com/jthegedus/asdf-gcloud/issues/68#issuecomment-1561070191 works for you? I've browsed a bit and it seems that the issue affects only MacOS. I know that it's using some legacy version of Bash by default. I couldn't reproduce this issue with Bash 5.2.15. I want to keep errexit and pipefail flags, since they are in general useful for intercepting hidden errors.


GDScript duplicate arguments bug fixed

Fix: #35206
and there was a typo in core/error_macros.h after the PR #33391 also fixed

and there was a typo in core/error_macros.h after the PR #33391 also fixed

Could you make a separate PR for this? It's unrelated to the GDScript change.

I've created a separate PR for the error_macro.h typo : #36783

Thanks!

Cherry-picked for 3.2.2.


Add landuse encoded value based on closed-ring ways tagged with landuse=*

I built a quick prototype, which:

stores the way tags and OSM node Ids for all OSM ways tagged with landuse=* in memory during the first pass of OSMReader

finds all the corresponding node coordinates in the second pass

builds an area index for all these (closed-ring) polygons before we read the OSM ways again in the second pass

finds the areas each edge is contained in and feeds them to the tag parsers

adds a tag parser for the new landuse encoded value, which uses the smallest of these areas to set the landuse value

This way we can, e.g., use custom models that prefer forest areas, or slow down the speed in residential areas etc.
We can also just look at the landuse values using path details:

My first quick test resulted in an import time of 117s compared to 80s for a map of Bavaria with the master branch.
The biggest issue I ran into so far was that landuse areas are often mapped as multipolygons many forest areas seem to be mapped as relations with such polygons as members. Parsing the relations wouldn't be much harder, but since we only get to see them at the end of the first pass (after the ways) we would have to read the OSM file a third time :(

The biggest issue I ran into so far was that many forest areas seem to be mapped as relations with such polygons as members.

The OSM wiki even says that landuse should not be tagged on relations, but there are currently around 1.8mio such relations in OSM :(

I added support for multipolygon landuse relations in my second commit (using a third pass of the OSM file). At least for Bavaria this improves the handling of landuse=forest a lot. Here is a bike route that tries to stay in the forest as much as possible:

This branch looks very promising, although it is quite expensive in terms of RAM and preparation time. I tested the extract for Austria with four bicycle profiles active and had to increase the RAM size from 3GB to 5GB.
I just noticed a litte draw-back and this is that in some areas the way does not overlap with the landuse polygon, it is just very very close. In such cases it would be great if it would be possible to utilize the near by landuse polygon. Do you see the possibility for an enhancment to take a lets say a 20 meters margin into account?

I just noticed a litte draw-back and this is that in some areas the way does not overlap with the landuse polygon, it is just very very close. In such cases it would be great if it would be possible to utilize the near by landuse polygon. Do you see the possibility for an enhancment to take a lets say a 20 meters margin into account?

Yes, maybe that is actually quite a good idea. Also because in some cases for example forest areas are separated by roads like here:

even though the road clears leads 'through' the forest.

Should be doable using jts? https://locationtech.github.io/jts/javadoc/org/locationtech/jts/operation/buffer/BufferOp.html

Should be doable using jts?

I did not look into it yet, but yes this sounds like what we need, thanks! Precision isn't very important for us here I think, we just need to widen the polygons a bit. The tricky part might be dealing with overlapping landuse polygons then.

JTS should be able to properly merge them.

JTS should be able to properly merge them.

I meant landuse polygons with different tag values. For example when a road is located near the border between an forest and a farmland area and we extend both polygons we need to decide which landuse value we like to use for this road.
Btw here is a nice visualization of the landuse tag: https://osmlanduse.org

I thought you meant overlapping parts of multipolygons. Aren't different overlapping landuse polygons already quite common? It would be nice if they weren't and everyone made proper multipolygons with holes in them, but in reality there's going to be quite a lot of overlap.
You'll most likely need to define some kind of sorting behaviour. e.g preferring non-buffered matches and polygons with a smaller area.

It's probably easier to leave the polygons as they are and instead make the search a little less precise.

I'd love to see a follow up PR that uses the landuse information to augment the urban density EV.

I created PR #2812 which implements the mentioned search buffer from above. @easbar Can you please check?

although it is quite expensive in terms of RAM and preparation time. I tested the extract for Austria with four bicycle profiles active and had to increase the RAM size from 3GB to 5GB.

The RAM requirement should be much lower now, can you please try again? Note that I also removed the relation handling for now, and maybe do this in a follow-up.

Also because in some cases for example forest areas are separated by roads like here

The same problem exists for residential areas where roads might be excluded explicitly from the residential landuse areas, like here (extract from Berlin):

Then again, in these cases the roads are probably often tagged as highway=residential, too.

Querying with a buffer like you proposed should fix this.

Yes, it does:


Adding Owasys owa5X

This is a PR requested by<EMAIL_ADDRESS>to add our Owasys owa5X device

Hi, can you squash these 2 commits in just 1 please?

In addition to squashing the commits can you also make sure you add a Change-type like in the example highlighted in the doc? https://github.com/balena-os/meta-balena/blob/master/contributing-device-support.md#step-3-hardware-contract ? The example is this one https://github.com/balena-io/contracts/pull/296


Added Contact Information

Added Ahmeds picture and contact information as well as changed the API key

contact info addition was added. thx!


"waiting for javascript"

Hello,
I installed h5p component, plugins and libraries for joomla from github on my site.
It seems it works, but "waiting for javascript" (printscreen is joined) is indicated.
the site is in joomla 5.2.1, php 8.2.15
Tried with firefox and chrome, javascript is enable.
Please, can you help me ?
Thanks a lot !

Hi!
In current version 1.02 not create file in path: /libraries/h5p/.htaccess
download: https://github.com/ItalikDev/H5P-Joomla/blob/master/lib_h5p/.htaccess
and place to  /libraries/h5p.
It will be fixed in the next version.
Vitalii.

It works ! Thanks a lot !


LDAP configuration help

Hi
I am struggling to get the wherehows frontend authentication to work against my LDAP server. I wonder if anyone would be so kind as to review my config?
First proof that LDAP is able to authenticate the user using command line utilities on the same machine that the wherehows docker image is running:

ldapwhoami -vvv -h localhost -p 389 -D uid=george,ou=People,dc=example,dc=com -x -w
ldap_initialize( ldap://localhost:389 )
dn:uid=george,ou=People,dc=example,dc=com
Result: Success (0)

Next my .env LDAP related settings:
LDAP
WHZ_LDAP_URL=ldap://localhost:389
<EMAIL_ADDRESS>WHZ_LDAP_SEARCH_BASE=ou=People,dc=example,dc=com
And the stack trace when I login to the front end with the ID and password that I have verified against LDAP:
wherehows-frontend_1       | 2018-04-22 02:59:16 INFO  application:85 - Creating DAO factory: wherehows.dao.DaoFactory
wherehows-frontend_1       | 2018-04-22 02:59:16 ERROR application:183 - Piwik site ID must be an integer
wherehows-frontend_1       | 2018-04-22 02:59:40 ERROR application:96 - Ldap server connection error!
wherehows-frontend_1       | javax.naming.CommunicationException: localhost:389
wherehows-frontend_1       | 	at com.sun.jndi.ldap.Connection.(Connection.java:226) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) ~[na:1.8.0_162]
wherehows-frontend_1       | 	at javax.naming.InitialContext.init(InitialContext.java:244) ~[na:1.8.0_162]

Have you got an error with this config file??

Dear issue owner,
Thanks for your interest in WhereHows. We have recently announced DataHub which is the rebranding of WhereHows. LinkedIn improved the architecture of WhereHows and rebranded WhereHows into DataHub and replaced its metadata infrastructure in this direction. DataHub is a more advanced and improved metadata management product compared to WhereHows.
Unfortunately, we have to stop supporting WhereHows to better focus on DataHub and offer more help to DataHub users. Therefore, we will drop all issues related to WhereHows and will not accept any contribution for it. Active development for DataHub has already started on datahub branch and will continue to live in there until it's finally merged to master and project is renamed to DataHub.
Please check the datahub branch to get familar with DataHub.
Best,
DataHub team


fp16 support

This PR includes fp16 support for the following modules:

SpatialConvolution
all point-wise activations
all 2d pooling operations
all softmax
SpatialCrossMapLRN
SpatialDivisiveNormalization

Requires merge of torch/cutorch#394 first.

Does cuDNN support operations on fp16 weights and float inputs?

@apaszke no, everything should be the same type

for reference, here is my version that I rebased on R5 https://github.com/soumith/cudnn.torch/compare/R5...szagoruyko:fp16
I will do a PR when I finish writing tests for all modules.

Hm, I think this implementation won't throw any errors if you have such situation. It will just reinitialise input descriptors without checking if their type matches the weight type.

@szagoruyko +1 For cudnn.typemap

@apaszke You actually cannot compute with fp16 on pre-Pascal GPUs except for the X1. cuDNN supports the following configs:

double data, double computations
single data, single computation
half data, single computation
half data, half computation

@lukasc-ch Well, there are 3 types there: input, weight and computation. I agree that cuDNN doesn't support halfs for computation on pre-Pascal architectures, but my question was, what happens if you have float input and half weights - is this supported? It doesn't seem to be checked by your implementation.

The dilemma that I have now is that there are two PRs (which is why it is nice to pre-declare that you are working on the feature). One by @lukasc-ch and other by @szagoruyko . Sergey's is much cleaner in design, it introduces a typemap and shape that keep the rest of the code fairly generic. However it is not complete yet. I think we can integrate the needed parts of @lukasc-ch 's PR into Sergey's and merge it in.
Does everyone else on the thread agree?

@soumith yes, this makes sense :+1:
@apaszke no, this is not supported, at least not yet :)

PR #206 replaces this. Closing it.


watchOS 4 support?

I read somewhere that this package has no minimum requirements however when I tried to include in a package that supports watchOS 4, Xcode generates warnings that this package requires watchOS 5.
Information

1.1.2: What tag or branch of swift-collections are you using?
macOS 14.5: Please tell us the version number of your operating system.
5.10: Paste the output of swift --version here.
Xcode Version 15.4 (15F31d)

Checklist

[x] If possible, I've reproduced the issue using the main branch of this package.
[x] I've searched for existing GitHub issues.

Steps to Reproduce
Create a swift package that has a minimum requirement of watchOS 4 (like https://github.com/kudit/Compatibility)
Attempt to build Watch App target.
Expected behavior
inclusion is fine and compiles in Xcode with no errors.
Actual behavior
Xcode reports the following error:
The package product 'OrderedCollections' requires minimum platform version 5.0 for the watchOS platform, but this target supports 4.0

This package does not intentionally set a minimum deployment target.
Do you happen to know where the watchOS 5 minimum comes from?

The description is about creating a swift package, and I can't reproduce this with a swift package with Xcode 15.4.
However I am seeing something similar but not identical, using the same version of Xcode. I opened a new watchOS project for a library, then added swift-collections (1.1.3). I set the watchOS deployment target to the lowest available (watchOS 4). Upon building, I see:
ld: warning: object file (<path>/Build/Products/Debug-watchos/OrderedCollections.o) was built for newer watchOS version (5.0) than being linked (4.0)
ld: warning: object file (<path>/Build/Products/Debug-watchos/InternalCollectionsUtilities.o) was built for newer watchOS version (5.0) than being linked (4.0)

For what it's worth with no change in project settings, this does not happen in the current Xcode 16 beta.

This is by design. See https://github.com/swiftlang/swift-package-manager/issues/6974#issuecomment-2071152417


GraphQL Tracker improvements

Closes #911
Closes #916
Description
The GraphQL tracker we made originally was a quick PoC and had some issues. This PR changes the implementation to a more robust version that traverses the query AST to get extra information.

Disable tracker by default and provide a Logger option to enable it (like all the other cache/header logs).
Show all the property path: shop.products.handle instead of just handle.
Handle aliases in queries.
Handle fragment spreads in queries.
Show file and location of the query.
Trim the logs when there are too many unused properties.

Additional context
The code is more complex than before because we can't rely on simple JSON revivers anymore. I would recommend checking the tests and the comments to understand what's going on. It should all be tree-shaked during build, in any case.
The easiest way to test this is adding the following to App.server.jsx:
// @ts-ignore
globalThis.__logger = {
  // @ts-ignore
  ...globalThis.__logger,
  options: () => ({
    showUnusedQueryProperties: true,
  }),
};

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[x] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

For enabling the GraphQL tracker, my first option was passing it to renderHydrogen(..., { }) options. However, I saw all the other logs (cache, perf, etc) are using options in the Logger so I've implemented it there.
We can change it if anyone has a different opinion.


Clean EventHandler on stop

To fix possible crashes when player-related (e.g. onPrepared) callbacks are fired on already stopped player with thread==null.

Thanks, can you tell me an example of how such a crash can happen?

It could happen when one uses setOnPreparedListener to e.g. start player but, stop already occurred a bit before and event preparation event was posted to handler. Completely struggled with it, checked locally - seems to work ok.

I unfortunately could never reproduce this issue. With all the rewrites in the player core, I hope it is solved anyway.


dc_to_pe and pedestal arrays should contains numpy.float32 type.

Dear ctapipe devs,
event.mc.tel[telid].dc_to_pe and event.mc.tel[telid].pedestal Numpy ndarray contain numpy.float64 elements. This is because these variables are deeclared as double in simtel
From our point of view, we do not need such precision and we can gain a important speed up factor if we declare them as numpy.float32 (in pyhessio).

I confirm that if pyhessio is updated, we don't need to make any special changes.
I take care of that in pyhessio.
I just wanted to inform ctapipe users that these formats will change.


Develop a book's retail area.

Backend

Create a new model to hold distribution expenses
Can be expandable to other retail information

Frontend

Change the book pages to add distribution expenses

 Develop a book's retail area.


New package: bloodrock.pkg-config-lite version 0.28-1

Description

Resolve https://github.com/microsoft/winget-pkgs/issues/123550

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Logs
Local device
PS D:\Workloads\winget-pkgs> .\Tools\SandboxTest.ps1 .\b\bloodrock\pkg-config-lite\0.28-1\
--> Validating Manifest
清单验证成功。

--> Checking dependencies
--> Starting Windows Sandbox, and:
    - Mounting the following directories:
      - C:\Users\Administrator\AppData\Local\Temp\SandboxTest as read-only
      - D:\Workloads\winget-pkgs as read-and-write
    - Installing WinGet
    - Configuring Winget
    - Installing the Manifest 0.28-1
    - Refreshing environment variables
    - Comparing ARP Entries

Windows Sandbox
--> Installing WinGet
--> Disabling safety warning when running installer
Tip: you can type 'Update-EnvironmentVariables' to update your environment variables, such as after installing a new software.

--> Configuring Winget
Enabled admin setting 'LocalManifestFiles'.
Enabled admin setting 'LocalArchiveMalwareScanOverride'.

--> Installing the Manifest 0.28-1

Found Pkg Config Lite [bloodrock.pkg-config-lite] Version 0.28-1
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://zenlayer.dl.sourceforge.net/project/pkgconfiglite/0.28-1/pkg-config-lite-0.28-1_bin-win32.zip
  ██████████████████████████████  46.5 KB / 46.5 KB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Starting package install...
Command line alias added: "pkg-config"
Path environment variable modified; restart your shell to use the new value.
Successfully installed

--> Refreshing environment variables

--> Comparing ARP Entries

DisplayName     DisplayVersion Publisher ProductCode                              Scope
-----------     -------------- --------- -----------                              -----
Pkg Config Lite 0.28-1         bloodrock bloodrock.pkg-config-lite__DefaultSource User

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> pkg-config.exe --help
Usage:
  pkg-config.exe [OPTION...]

Help Options:
  -h, --help                              Show help options

Application Options:
  --version                               output version of pkg-config
  --modversion                            output version for package
  --atleast-pkgconfig-version=VERSION     require given version of pkg-config
  --libs                                  output all linker flags
  --static                                output linker flags for static linking
  --short-errors                          print short errors
  --libs-only-l                           output -l flags
  --libs-only-other                       output other libs (e.g. -pthread)
  --libs-only-L                           output -L flags
  --cflags                                output all pre-processor and compiler flags
  --cflags-only-I                         output -I flags
  --cflags-only-other                     output cflags not covered by the cflags-only-I option
  --variable=NAME                         get the value of variable named NAME
  --define-variable=NAME=VALUE            set variable NAME to VALUE
  --exists                                return 0 if the module(s) exist
  --print-variables                       output list of variables defined by the module
  --uninstalled                           return 0 if the uninstalled version of one or more module(s) or their dependencies will be used
  --atleast-version=VERSION               return 0 if the module is at least version VERSION
  --exact-version=VERSION                 return 0 if the module is at exactly version VERSION
  --max-version=VERSION                   return 0 if the module is at no newer than version VERSION
  --list-all                              list all known packages
  --debug                                 show verbose debug information
  --print-errors                          show verbose information about missing or conflicting packages (default unless --exists or --atleast/exact/max-version given on the command line)
  --silence-errors                        be silent about errors (default when --exists or --atleast/exact/max-version given on the command line)
  --errors-to-stdout                      print errors from --print-errors to stdout not stderr
  --print-provides                        print which packages the package provides
  --print-requires                        print which packages the package requires
  --print-requires-private                print which packages the package requires for static linking
  --dont-define-prefix                    don't try to override the value of prefix for each .pc file found with a guesstimated value based on the location of the .pc file
  --prefix-variable=PREFIX                set the name of the variable that pkg-config automatically sets
  --msvc-syntax                           output -l and -L flags for the Microsoft compiler (cl)

@wingetbot waivers Add Validation-Executable-Error Validation-Unapproved-URL


Metadata of video

Is there a way we can extract video metadata, and in particular:

Publication date
number of views
description
number of likes

You can extract this data with
publish_date()
description() and
views_count()
But you dont have extract the likes number.

>>> from pytubefix import YouTube
>>>
>>> yt = YouTube("https://www.youtube.com/watch?v=YL9apblSQ-s")
>>> print(yt.publish_date)

2024-07-14 09:00:17-07:00
>>> print(yt.description)
I made this beat, wrote this song & shot the video last night.
DOWNLOAD SONG: https://geo.itunes.apple.com/us/album/you-missed-single/1757316416?ls=1&app=itunes
ALBUMS & MERCH: http://www.HangOverGang.com

Tom MacDonald - "You Missed"

SUBSCRIBE TO THIS CHANNEL &  CONNECT W/ TOM MACDONALD!
FACEBOOK: http://www.facebook.com/TomMacDonaldOfficial
INSTAGRAM: http://www.instagram.com/hangovergang
TWITTER: http://www.twitter.com/IAmTomMacDonald
WEBSITE: http://www.hangovergang.com
SPOTIFY: http://spoti.fi/2H35BQR
iTUNES: https://apple.co/2BQucZO

WRITTEN BY Tom MacDonald
BEAT PRODUCED BY Tom MacDonald

MIXED & MASTERED by Evan Morgan
http://www.evanmorganproductions.com
http://www.youtube.com/user/emorganproductions
http://www.instagram.com/EMorganProductions

#TomMacDonald #Trump #YouMissed
>>> print(yt.views)
7039811
>>>
>>>
>>>

>>> from pytubefix import YouTube
>>>
>>> yt = YouTube("https://www.youtube.com/watch?v=R6U082HemyA")
>>> print(yt.publish_date)

2023-08-22 06:03:03-07:00
>>> print(yt.description)
Inside The $3 Million Cessna Grand Caravan EX Plane

0:00 - Intro
This is the Cessna Grand Caravan EX, an aircraft that maintains its 208B designation, but gives operators a great deal more power, thanks to a new Pratt & Whitney turboprop engine developed expressly for the EX. Today we’re going inside the Cessna Grand Caravan EX to talk about everything you need to know about this legendary aircraft.

0:47 - Cabin
Likewise, you have plenty of choices when outfitting a Cessna Grand Caravan EX's cabin. Cessna typically will not sell this airplane with a finished interior, because many buyers choose to customize it. The cabin has a width of 5 feet 4 inches or 1.63 meters. While height is 4 feet 6 inches or 1.37 meters, length is 21 feet 4 inches or 6.5 meters. There are four exterior doors-one at each pilot position plus an air-stair passenger door aft right and an oversized, fold-up and fold-out cargo door aft left.
While the Cessna Grand Caravan EX can seat a maximum of 14 people, in executive configuration the airplane seats six to eight passengers, plus one or two pilots. The single seats have the same swivel and recline features and similar rich veneers and fabrics. You can install in-flight entertainment systems that almost match those in the priciest business jets, too.
On most executive Caravans, the lavatory consists of a flip-up part of the rear bench seat and an underlying and dreaded chemical bowl. However, some Caravans have been equipped with electric flushing toilets, full vanities and sinks, and even exterior plug-ins for showering, and generator power. Some have also been outfitted with elaborate bars and microwave ovens.

2:37 - Cockpit
The Cessna Grand Caravan EX’s cockpit is comfortably spacious, more like a small business aircraft than a light airplane, and it is both utilitarian and well-appointed.
An integrated glass cockpit is pretty much a standard requirement these days, and the Caravan has long featured Garmin’s G1000 flight deck, now delivered in the NXi version with faster processors and added features such as visual approaches and HSI map overlays. ADS-B OUT is standard, and ADS-B IN is optional. VFR and IFR charts can also now be displayed on the moving map. Garmin’s SurfaceWatch alerts pilots if they are about to take off or land on the wrong runway or on a taxiway or too short a runway. Noteworthy is the newest feature that comes with NXi, the com frequency decoding.
Caravans are approved for flight into known icing when equipped with the TKS ice-protection system. The TKS tank holds 20 gallons or 75 liters and provides 3.5 hours of normal anti-icing operation or 45 minutes at the high-flow setting. The propeller has its own TKS slinger ring, which helps protect the nose of the airplane. The windshield also is protected with a TKS spray bar. The TKS system is much cleaner looking than the deicer boot system found on earlier Caravans, which had boots mounted on almost every forward-facing surface.

4:42 - Engine and Performance
The Cessna Grand Caravan EX's new Pratt & Whitney PT6A-140 has a TBO of 4,000 hours and an average hourly fuel burn of 60 gallons or 230 liters, and coupled with a McCauley 4-blade aluminum, constant speed, full feathering propeller, brings a lot more power, which does good things all around for the Cessna Grand Caravan EX.
Arguably the most noteworthy enhancement is the Caravan’s improved climb rate, which is 1,275 feet per minute or 389 meters per minute. The useful load is 3,532 lbs or 1,602 kg, and the full-fuel payload is 1,286 lbs or 583 kg.
The Grand Caravan EX needs just 2,160 feet or 658 meters to clear a 50-foot-tall obstacle. Landing distance is 1,836 feet or 560 meters, landing speeds are nearly identical, and the maximum operating altitude is 25,000 feet or 7,620 meters.
Range is slightly lower on the EX, but full tanks will get you 832 no-wind nautical miles down the road, and a maximum range of 912 nautical miles or 1,689 kilometers.
With a true airspeed of right around 195 knots, the EX is about 15 knots faster than its predecessor. With the big cargo pod below, that top speed drops by as much as 10 knots.

8:43 - Purchase and Charter Price
The base purchase price for a new Cessna Grand Caravan EX is $2.7 million before options, and the charter price ranges between $1,600 and $2,000 per hour. Naturally, prices will vary depending on availability, fuel prices, ground fees, and more.

9:02 - Operating Cost
While the total fixed cost is roughly $180,000 to $220,000 per year, the average hourly operating cost is estimated at $1,200 to $1,500.

9:14 - Outro

Aviation Base is your favorite source for your daily dose of aviation videos: private jet reviews, as well as private jet interior, both cabin, and cockpit, along with turboprops, commercial planes, and helicopters. We also make videos about private jet charter, private jet price, and private jet cost. Subscribe so you don't miss any videos from us!
>>> print(yt.views)
57285
>>>
>>>
>>>

Thank you very much!


Crop empty space at the bottom of the last spritesheet in multi sheet situations

implemented with v0.7.0


UI: Updated in settings

Follows from #21036

Adds the Last Update Time label in the developer settings.

Clicking on Last Update Time sends a SIGHUP to updated.

The description of the Version label is the release notes.

I had to modify the constructor of LabelControl in order to add a description to some labels.
Let me know if something is wrong/bad with this

Thanks for the PR!


Example needs  tags

I think the first example in the README is missing  tags:
          <Card
            exact
            path="/"
            render={() => <Link to="/hello"><Text>Press it</Text></Link>}
          />

PR welcomed ! 🙏 😄


[No QA] Tag mobile deployers instead of @here in #announce for deploy failures

@AndrewGable will you please review?
Details
This PR updates the pings in #announce to ping mobile deployers instead of @here for workflow failures. Got the mobile deployer subgroup from https://github.com/Expensify/Mobile-Deploy/blob/master/notify.js#L114
Fixed Issues
Discussion in https://expensify.slack.com/archives/C03V9A4TB/p1629476458374500
Tests
N/A, will confirm this live
QA Steps
N/A

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by @roryabraham in version: 1.0.88-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅