no main packages to build

I'm new in knative, and trying to run golang hello  kn func example on my local,
I faced with the error below and want to solve it:
The error that i got:
Paketo Buildpack for Go Build 2.1.1
  Executing build process
    Running 'go build -o /layers/paketo-buildpacks_go-build/targets/bin -buildmode pie -trimpath .'
      go: no main packages to build
      Failed after 364ms
failed to execute 'go build': exit status 1
Timer: Builder ran for 13.495298381s and ended at 2023-11-29T16:16:30Z
ERROR: failed to build: exit status 1
Error: executing lifecycle: failed with status code: 51
Error: exit status 1

the other details as below:
My Local: MacBook Pro, Chip: Apple M2 Pro

$docker version
Client:
 Cloud integration: v1.0.35+desktop.5
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:28:49 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.24.2 (124339)
 Engine:
  Version:          24.0.6
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       1a79695
  Built:            Mon Sep  4 12:31:36 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.22
  GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:          1.1.8
  GitCommit:        v1.1.8-0-g82f18fe
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$kn version
    Version:      v1.12.0
    Build Date:   2023-10-25 15:45:39
    Git Revision: ae357368
    Supported APIs:
    * Serving
      - serving.knative.dev/v1 (knative-serving v1.12.0)
    * Eventing
      - sources.knative.dev/v1 (knative-eventing v1.12.0)
      - eventing.knative.dev/v1 (knative-eventing v1.12.0)

kn func version
    v0.38.0-99-gcd0bc6ae

in the hello directory I run  as "kn func build --registry=docker.io/muhsinozbek --verbose"
And the output of the command is:

Pulling image ghcr.io/knative/builder-jammy-tiny:latest
latest: Pulling from knative/builder-jammy-tiny
Digest: sha256:8410d85ab825ae888b839c6dda95ea7d3f2cca3065c487e501f48bd7117af692
Status: Image is up to date for ghcr.io/knative/builder-jammy-tiny:latest
Selected run image index.docker.io/paketobuildpacks/run-jammy-tiny:latest
Pulling image index.docker.io/paketobuildpacks/run-jammy-tiny:latest
latest: Pulling from paketobuildpacks/run-jammy-tiny
Digest: sha256:3a5840769245a963b17e9352e19cc7e21bb671dfe262da9c3b3e8178f9c847a0
Status: Image is up to date for paketobuildpacks/run-jammy-tiny:latest
Creating builder with the following buildpacks:
-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>Using build cache volume pack-cache-muhsinozbek_hello_latest-2c8044f3e589.build
Running the creator on OS linux with:
Container Settings:
  Args: /cnb/lifecycle/creator -daemon -launch-cache /launch-cache -log-level debug -app /workspace -cache-dir /cache -run-image index.docker.io/paketobuildpacks/run-jammy-tiny:latest -gid 0 index.docker.io/muhsinozbek/hello:latest
  System Envs: CNB_PLATFORM_API=0.12
  Image: pack.local/builder/67627074706570636962:latest
  User: root
  Labels: map[author:pack]
Host Settings:
  Binds: pack-cache-muhsinozbek_hello_latest-2c8044f3e589.build:/cache /var/run/docker.sock:/var/run/docker.sock pack-cache-muhsinozbek_hello_latest-2c8044f3e589.launch:/launch-cache pack-layers-aycuqazocl:/layers pack-app-okstuiqbga:/workspace
  Network Mode:
Starting creator...
Parsing inputs...
Ensuring privileges...
Executing command...
===> ANALYZING
Timer: Analyzer started at 2023-11-29T16:17:17Z
Image with name "index.docker.io/muhsinozbek/hello:latest" not found
Found image with identifier "d5daf29d8f277cf4f2e2208bc92bc42c6cb0e100bc535d3561c75977ebfe8b94"
Timer: Analyzer ran for 1.430916ms and ended at 2023-11-29T16:17:17Z
Run image info in analyzed metadata is:
{"Reference":"d5daf29d8f277cf4f2e2208bc92bc42c6cb0e100bc535d3561c75977ebfe8b94","Image":"index.docker.io/paketobuildpacks/run-jammy-tiny:latest","Extend":false,"target":{"os":"linux","arch":"arm64"}}
===> DETECTING
Timer: Detector started at 2023-11-29T16:17:17Z
Checking for match against descriptor: {linux amd64  [{ubuntu 18.04}]}
======== Output<EMAIL_ADDRESS>========
SKIPPED: No procfile found from either source path or binding.
======== Results ========
pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Error<EMAIL_ADDRESS>========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64","distros":[{"name":"ubuntu","version":"18.04"}]}]
======== Results ========
pass<EMAIL_ADDRESS>err<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
SKIPPED: project.clj could not be found in /workspace/project.clj
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_EXCLUDE_FILES                                                                       colon separated list of glob patterns, matched source files are removed
    $BP_GRADLE_ADDITIONAL_BUILD_ARGUMENTS                                                   the additionnal arguments (appended to BP_GRADLE_BUILD_ARGUMENTS) to pass to Gradle
    $BP_GRADLE_BUILD_ARGUMENTS             --no-daemon -Dorg.gradle.welcome=never assemble  the arguments to pass to Gradle
    $BP_GRADLE_BUILD_FILE                                                                   the location of the main build config file, relative to the application root
    $BP_GRADLE_BUILT_ARTIFACT              build/libs/*.[jw]ar                              the built application artifact explicitly.  Supersedes $BP_GRADLE_BUILT_MODULE
    $BP_GRADLE_BUILT_MODULE                                                                 the module to find application artifact in
    $BP_GRADLE_INIT_SCRIPT_PATH                                                             the path to a Gradle init script file
    $BP_INCLUDE_FILES                                                                       colon separated list of glob patterns, matched source files are included
    $BP_JAVA_INSTALL_NODE                  false                                            whether to install Yarn/Node binaries based on the presence of a package.json or yarn.lock file
    $BP_NODE_PROJECT_PATH                                                                   configure a project subdirectory to look for `package.json` and `yarn.lock` files
SKIPPED: No plans could be resolved
======== Output<EMAIL_ADDRESS>========
SKIPPED: build.sbt could not be found in /workspace/build.sbt
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_EXECUTABLE_JAR_LOCATION         a glob specifying which jar files should be used
    $BP_LIVE_RELOAD_ENABLED      false  enable live process reload in the image
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_DATADOG_ENABLED    false  whether to contribute the Datadog trace agent
  Launch Configuration:
    $BPL_DATADOG_DISABLED  false  whether to disable the Datadog trace agent (Java only!)
SKIPPED: variable 'BP_DATADOG_ENABLED' not set to true
======== Output<EMAIL_ADDRESS>========
SKIPPED: No procfile found from either source path or binding.
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_IMAGE_LABELS       arbitrary image labels
    $BP_OCI_AUTHORS        the org.opencontainers.image.authors image label
    $BP_OCI_CREATED        the org.opencontainers.image.created image label
    $BP_OCI_DESCRIPTION    the org.opencontainers.image.description image label
    $BP_OCI_DOCUMENTATION  the org.opencontainers.image.documentation image label
    $BP_OCI_LICENSES       the org.opencontainers.image.licenses image label
    $BP_OCI_REF_NAME       the org.opencontainers.image.ref.name image label
    $BP_OCI_REVISION       the org.opencontainers.image.revision image label
    $BP_OCI_SOURCE         the org.opencontainers.image.source image label
    $BP_OCI_TITLE          the org.opencontainers.image.title image label
    $BP_OCI_URL            the org.opencontainers.image.url image label
    $BP_OCI_VENDOR         the org.opencontainers.image.vendor image label
    $BP_OCI_VERSION        the org.opencontainers.image.version image label
SKIPPED: No supported environment variables were set
======== Results ========
pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>Resolving plan... (try #1)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #2)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #3)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused upx
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #4)
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #5)
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #6)
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #7)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #8)
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #9)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #10)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #11)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #12)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #13)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #14)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #15)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #16)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #17)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #18)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #19)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #20)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #21)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #22)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #23)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #24)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #25)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #26)
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #27)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #28)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #29)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #30)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #31)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #32)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #33)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused upx
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #34)
skip<EMAIL_ADDRESS>provides unused upx
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #35)
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #36)
skip<EMAIL_ADDRESS>provides unused upx
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #37)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #38)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #39)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #40)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused upx
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #41)
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #42)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused upx
fail<EMAIL_ADDRESS>provides unused native-image-application
Resolving plan... (try #43)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #44)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #45)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #46)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #47)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #48)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #49)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #50)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #51)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #52)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #53)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #54)
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #55)
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #56)
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #57)
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #58)
fail<EMAIL_ADDRESS>requires native-image-builder
Resolving plan... (try #59)
fail<EMAIL_ADDRESS>requires native-processed
Resolving plan... (try #60)
fail<EMAIL_ADDRESS>requires native-image-builder
======== Output<EMAIL_ADDRESS>========
SKIPPED: project.clj could not be found in /workspace/project.clj
======== Output<EMAIL_ADDRESS>========
SKIPPED: no 'deps.edn' file found in the application path
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_EXCLUDE_FILES                                                                       colon separated list of glob patterns, matched source files are removed
    $BP_GRADLE_ADDITIONAL_BUILD_ARGUMENTS                                                   the additionnal arguments (appended to BP_GRADLE_BUILD_ARGUMENTS) to pass to Gradle
    $BP_GRADLE_BUILD_ARGUMENTS             --no-daemon -Dorg.gradle.welcome=never assemble  the arguments to pass to Gradle
    $BP_GRADLE_BUILD_FILE                                                                   the location of the main build config file, relative to the application root
    $BP_GRADLE_BUILT_ARTIFACT              build/libs/*.[jw]ar                              the built application artifact explicitly.  Supersedes $BP_GRADLE_BUILT_MODULE
    $BP_GRADLE_BUILT_MODULE                                                                 the module to find application artifact in
    $BP_GRADLE_INIT_SCRIPT_PATH                                                             the path to a Gradle init script file
    $BP_INCLUDE_FILES                                                                       colon separated list of glob patterns, matched source files are included
    $BP_JAVA_INSTALL_NODE                  false                                            whether to install Yarn/Node binaries based on the presence of a package.json or yarn.lock file
    $BP_NODE_PROJECT_PATH                                                                   configure a project subdirectory to look for `package.json` and `yarn.lock` files
SKIPPED: No plans could be resolved
======== Output<EMAIL_ADDRESS>========
SKIPPED: build.sbt could not be found in /workspace/build.sbt
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_EXECUTABLE_JAR_LOCATION         a glob specifying which jar files should be used
    $BP_LIVE_RELOAD_ENABLED      false  enable live process reload in the image
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_JAVA_APP_SERVER                             the application server to use
    $BP_TOMCAT_CONTEXT_PATH                         the application context path
    $BP_TOMCAT_ENV_PROPERTY_SOURCE_DISABLED  false  Disable Tomcat's EnvironmentPropertySource
    $BP_TOMCAT_EXT_CONF_SHA256                      the SHA256 hash of the external Tomcat configuration archive
    $BP_TOMCAT_EXT_CONF_STRIP                0      the number of directory components to strip from the external Tomcat configuration archive
    $BP_TOMCAT_EXT_CONF_URI                         the download location of the external Tomcat configuration
    $BP_TOMCAT_EXT_CONF_VERSION                     the version of the external Tomcat configuration
    $BP_TOMCAT_VERSION                       9.*    the Tomcat version
  Launch Configuration:
    $BPL_TOMCAT_ACCESS_LOGGING_ENABLED              the Tomcat access logging state
PASSED: a WEB-INF directory was not found, this is normal when building from source
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_JAVA_APP_SERVER                                   the application server to use
    $BP_TOMEE_CONTEXT_PATH                                the application context path
    $BP_TOMEE_DISTRIBUTION                  microprofile  the Tomee distribution
    $BP_TOMEE_ENV_PROPERTY_SOURCE_DISABLED  false         Disable Tomcat's EnvironmentPropertySource
    $BP_TOMEE_EXT_CONF_SHA256                             the SHA256 hash of the external Tomee configuration archive
    $BP_TOMEE_EXT_CONF_STRIP                0             the number of directory components to strip from the external Tomee configuration archive
    $BP_TOMEE_EXT_CONF_URI                                the download location of the external Tomee configuration
    $BP_TOMEE_EXT_CONF_VERSION                            the version of the external Tomee configuration
    $BP_TOMEE_VERSION                       8.*           the Tomee version
  Launch Configuration:
    $BPL_TOMEE_ACCESS_LOGGING_ENABLED                     the Tomee access logging state
PASSED: a WEB-INF directory was not found, this is normal when building from source
======== Output<EMAIL_ADDRESS>========
SKIPPED: No procfile found from either source path or binding.
======== Output<EMAIL_ADDRESS>========
SKIPPED: BP_JATTACH_ENABLED was not set to true
======== Output<EMAIL_ADDRESS>========
SKIPPED: no binding of type ApplicationInsights found
======== Output<EMAIL_ADDRESS>========
SKIPPED: no bindings of type 'StackdriverDebugger' or 'StackdriverProfiler' found
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_DATADOG_ENABLED    false  whether to contribute the Datadog trace agent
  Launch Configuration:
    $BPL_DATADOG_DISABLED  false  whether to disable the Datadog trace agent (Java only!)
SKIPPED: variable 'BP_DATADOG_ENABLED' not set to true
======== Output<EMAIL_ADDRESS>========
SKIPPED: BP_JMA_ENABLED was not set to true
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_IMAGE_LABELS       arbitrary image labels
    $BP_OCI_AUTHORS        the org.opencontainers.image.authors image label
    $BP_OCI_CREATED        the org.opencontainers.image.created image label
    $BP_OCI_DESCRIPTION    the org.opencontainers.image.description image label
    $BP_OCI_DOCUMENTATION  the org.opencontainers.image.documentation image label
    $BP_OCI_LICENSES       the org.opencontainers.image.licenses image label
    $BP_OCI_REF_NAME       the org.opencontainers.image.ref.name image label
    $BP_OCI_REVISION       the org.opencontainers.image.revision image label
    $BP_OCI_SOURCE         the org.opencontainers.image.source image label
    $BP_OCI_TITLE          the org.opencontainers.image.title image label
    $BP_OCI_URL            the org.opencontainers.image.url image label
    $BP_OCI_VENDOR         the org.opencontainers.image.vendor image label
    $BP_OCI_VERSION        the org.opencontainers.image.version image label
SKIPPED: No supported environment variables were set
======== Results ========
pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>Resolving plan... (try #1)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #2)
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #3)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #4)
skip<EMAIL_ADDRESS>provides unused watchexec
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #5)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #6)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #7)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #8)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #9)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #10)
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #11)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #12)
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #13)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #14)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #15)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #16)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #17)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #18)
skip<EMAIL_ADDRESS>requires jdk
skip<EMAIL_ADDRESS>provides unused watchexec
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #19)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #20)
skip<EMAIL_ADDRESS>requires jdk
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused node
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #21)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #22)
skip<EMAIL_ADDRESS>provides unused maven
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #23)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #24)
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused npm
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #25)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #26)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused watchexec
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #27)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused npm
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #28)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused watchexec
fail<EMAIL_ADDRESS>provides unused native-image-builder
Resolving plan... (try #29)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #30)
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused yarn
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #31)
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #32)
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application
fail<EMAIL_ADDRESS>provides unused jdk
Resolving plan... (try #33)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #34)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #35)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused node
fail<EMAIL_ADDRESS>provides unused maven
Resolving plan... (try #36)
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>requires jre
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>requires jvm-application
fail<EMAIL_ADDRESS>provides unused jdk
Resolving plan... (try #37)
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #38)
skip<EMAIL_ADDRESS>requires jdk
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused watchexec
fail<EMAIL_ADDRESS>provides unused node
Resolving plan... (try #39)
fail<EMAIL_ADDRESS>requires jdk
Resolving plan... (try #40)
skip<EMAIL_ADDRESS>requires jdk
skip<EMAIL_ADDRESS>provides unused npm
skip<EMAIL_ADDRESS>provides unused node
skip<EMAIL_ADDRESS>provides unused maven
skip<EMAIL_ADDRESS>provides unused yarn
skip<EMAIL_ADDRESS>provides unused watchexec
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application-package
skip<EMAIL_ADDRESS>requires jvm-application
fail<EMAIL_ADDRESS>provides unused jre
======== Output<EMAIL_ADDRESS>========
failed to find .git directory and no git credential service bindings present
======== Output<EMAIL_ADDRESS>========
SKIPPED: No procfile found from either source path or binding.
======== Output<EMAIL_ADDRESS>========
  Build Configuration:
    $BP_IMAGE_LABELS       arbitrary image labels
    $BP_OCI_AUTHORS        the org.opencontainers.image.authors image label
    $BP_OCI_CREATED        the org.opencontainers.image.created image label
    $BP_OCI_DESCRIPTION    the org.opencontainers.image.description image label
    $BP_OCI_DOCUMENTATION  the org.opencontainers.image.documentation image label
    $BP_OCI_LICENSES       the org.opencontainers.image.licenses image label
    $BP_OCI_REF_NAME       the org.opencontainers.image.ref.name image label
    $BP_OCI_REVISION       the org.opencontainers.image.revision image label
    $BP_OCI_SOURCE         the org.opencontainers.image.source image label
    $BP_OCI_TITLE          the org.opencontainers.image.title image label
    $BP_OCI_URL            the org.opencontainers.image.url image label
    $BP_OCI_VENDOR         the org.opencontainers.image.vendor image label
    $BP_OCI_VERSION        the org.opencontainers.image.version image label
SKIPPED: No supported environment variables were set
======== Results ========
pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>Resolving plan... (try #1)
fail<EMAIL_ADDRESS>provides unused ca-certificates
Resolving plan... (try #2)
skip<EMAIL_ADDRESS>provides unused watchexec
4 of 9 buildpacks participating
paketo-buildpacks/ca-certificates 3.6.6
paketo-buildpacks/go-dist         2.4.3
paketo-buildpacks/go-mod-vendor   1.0.26
paketo-buildpacks/go-build        2.1.1
Timer: Detector ran for 900.066042ms and ended at 2023-11-29T16:17:18Z
===> RESTORING
Timer: Restorer started at 2023-11-29T16:17:18Z
Restoring Layer Metadata
Reading buildpack directory: /layers/paketo-buildpacks_ca-certificates
Reading buildpack directory: /layers/paketo-buildpacks_go-dist
Reading buildpack directory: /layers/paketo-buildpacks_go-mod-vendor
Reading buildpack directory: /layers/paketo-buildpacks_go-build
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/paketo-buildpacks_ca-certificates
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/paketo-buildpacks_go-dist
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/paketo-buildpacks_go-mod-vendor
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/paketo-buildpacks_go-build
Timer: Restorer ran for 1.9145ms and ended at 2023-11-29T16:17:18Z
===> BUILDING
Timer: Builder started at 2023-11-29T16:17:18Z
Running build for buildpack<EMAIL_ADDRESS>Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command

Paketo Buildpack for CA Certificates 3.6.6
  https://github.com/paketo-buildpacks/ca-certificates
  Launch Helper: Contributing to layer
    Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
Processing layers
Updating environment
Reading output files
Updating buildpack processes
Updating process list
Finished running build for buildpack<EMAIL_ADDRESS>Running build for buildpack<EMAIL_ADDRESS>Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command
Paketo Buildpack for Go Distribution 2.4.3
  Resolving Go version
    Candidate version sources (in priority order):
      go.mod    -> ">= 1.14"
      <unknown> -> ""

    Selected Go version (using go.mod): 1.21.4

  Executing build process
    Installing Go 1.21.4
      Completed in 11.624s

  Generating SBOM for /layers/paketo-buildpacks_go-dist/go
      Completed in 2ms

Processing layers
Updating environment
Reading output files
Updating buildpack processes
Updating process list
Finished running build for buildpack<EMAIL_ADDRESS>Running build for buildpack<EMAIL_ADDRESS>Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command
Paketo Buildpack for Go Mod Vendor 1.0.26
  Executing build process
    Running 'go mod vendor'
      Completed in 700ms

  Generating SBOM for /workspace/go.mod
      Completed in 61ms

Processing layers
Updating environment
Reading output files
Updating buildpack processes
Updating process list
Finished running build for buildpack<EMAIL_ADDRESS>Running build for buildpack<EMAIL_ADDRESS>Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command
Paketo Buildpack for Go Build 2.1.1
  Executing build process
    Running 'go build -o /layers/paketo-buildpacks_go-build/targets/bin -buildmode pie -trimpath .'
      go: no main packages to build
      Failed after 363ms
Timer: Builder ran for 13.36658634s and ended at 2023-11-29T16:17:31Z
ERROR: failed to build: exit status 1

$kind version
kind v0.20.0 go1.21.1 darwin/arm64

cc @lkingland

I have same problem. node is ok, golang project have no main packages to build problem.
problem version:

v0.39.0-30-g7ebf92dc
v0.38.2-1-gd697f4b5

most probably it is because of os/arch constraints, the log is below:
======== Error<EMAIL_ADDRESS>========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64","distros":[{"name":"ubuntu","version":"18.04"}]}]
======== Results ========
pass<EMAIL_ADDRESS>err<EMAIL_ADDRESS>

/assign

Just wanted to mention that I am facing the same issue.

I just switched to an M2 this week and I see the same issue.
It was working fine last week on my Intel chip Mac.

paketo's buildpack do not support arm64 yet IIRC
You could use s2i build strategy that should be multi-arch.

You could use s2i build strategy that should be multi-arch.

Well unfortunately Go specifically is not supporting build with s2i, sorry.

@muhsin09 could you please verify this has been fixed?


fix: update the Create a new project form

Description
Updated the Create a new project form based on Pascale new design:

Looks good!
Personally I would prefer smaller paddings in the modal and reclaim more available spaces, but can chat about it later.


Support for multi-threaded composer update?

Is there any way to have support for multi-threaded composer update ? With a lot of private GitHub packages, this takes a very long time for us to run and it's also a much more common operation than composer install.

This plugin is not implemented by threads. "Pallarel" means non-blocking & multiprexing I/O by curl_multi.
You should use --prefer-dist option and create a tag or GitHub's "release" for private packages. (All requests will be HTTP/HTTPS.) Then, prestissimo plugin maybe works as well.
https://getcomposer.org/doc/03-cli.md

I don't think the question is really about threads, but applying the parallel downloads functionality to "composer update" so that updates will be faster, just like installs. Here's a chunk of the verbose output when updating:
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$contracts.json into cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-filp$whoops.json from cache
Downloading http://packagist.org/p/illuminate/http%24067a99c3ec6d1546a34b096738f8f27c1684377ebcba387cd026bf619492f433.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$http.json into cache
Downloading http://packagist.org/p/illuminate/routing%2421474039230bc93162e60116094890341f01e71ee28d9a4978b205a9cf9dbeab.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$routing.json into cache
Downloading http://packagist.org/p/illuminate/session%24c2994ee943284b4b232151d1417167751d9d860c1a929b7a76542794352ddcb1.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$session.json into cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-laravelcollective$html.json from cache
Downloading http://packagist.org/p/illuminate/container%24ff666d8924bcd030e2b1bcb452948462796197f2cb22e6a54b3a192f70a57886.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$container.json into cache
Downloading http://packagist.org/p/illuminate/pipeline%2493e0c92f8bd1fc49e86adb6e259cea2fba998ae1c9746cd75a26b1fa4c62ecaf.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-illuminate$pipeline.json into cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-phpdocumentor$reflection-docblock.json from cache
Downloading http://packagist.org/p/symfony/yaml%2429c652c45cef265e5ba2a29bdcfceec7227ed120bebfb041fe4d5be8ade651b7.json
Writing /home/andrew/.composer/cache/repo/https---packagist.org/provider-symfony$yaml.json into cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-sebastian$recursion-context.json from cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-sebastian$exporter.json from cache
Reading /home/andrew/.composer/cache/repo/https---packagist.org/provider-sebastian$diff.json from cache

Can those downloads be made parallel? I think that's what we're wondering. Correct me if I'm wrong.

@ahamilton9 It's difficult. Composer plugins cannot overwrite Composer\Repository\ComposerRepository class normally.
But prestissimo enables Keep-Alive for single-connection requests. This accelerate downloading time.
https://en.wikipedia.org/wiki/Keepalive

@hirak @ahamilton9
The thing which is taking a long time for us is requests to GitHub API.
Each package takes 10-20 seconds because there are many API calls made to api.github.com. If this can be made using curl_exec we could save many minutes on composer update. Everyone who are using VCS packages faces this issue.
# composer update
.....

Just curious, is this issue relevant to this PR https://github.com/composer/composer/pull/5293? Maybe it should clearly mention that this isn't related to composer update but only composer install.

@schmunk42 Excellent! We have been setting this on a per-package basis, but it's great to see it available as a global option in composer.json .


Removed legacy linkanalysis package

Coverage increased (+2.2%) to 53.873% when pulling 158cef83400f1f3a9e98c84c01ea7434dae9dc35 on aecio/remove-legacy-code into e7587b96651916636c9ab9e48e61aca8e9b3499d on master.


Update frontend for new search API

Update for new changes from #62 and #66 , documentation here

Closed in eee97e7


Region support

Hi,
I use 2LCS a lot, but now we are getting LCS project that are from the new regions in LCS such as Europe and Norway.
Any way that 2LCS can support projects from other that then United States?
/Flemming

The lcs.dynamics.com url is currently hard coded in a couple of files, see https://github.com/search?q=repo%3Amicrosoft%2F2LCS lcs.dynamics.com&type=code
A solution would at least require to make that configurable and expose that configuration somewhere in the ui. Not sure if further changes would be required.

A quick search and replace of lcs.dynamics.com to eu.lcs.dynamics.com works.
I can start an environment, login to rdp and application. But the 2 2lsc.exes share a data cache, so you have to do a logout and login to see the right environments.
/Torben

I played around with this and added some basic support for different regions in the parameters of 2LCS.
Note that after changing the urls, you need to log out and log in again.
If you want to test this version, you can go to release 0.31.0 in my fork and download a compiled version there (or just compile the pull request version yourself).
Unfortunately I currently do not have access to LCS projects that are not in the US/global region, so I can't test it fully myself.

When using these parameters

I get an logon error:

Thx for doing the development. I would like a picking list for Geo, as I will be going to work in both US and EU every day.

@flauest Thanks for testing!
For the LCS Diagnostic Url, your screenshot shows 2 dots after eu:
https://diag.eu..lca.dynamics.com
                ^

I also got issues (although different from what you describe) with this url value. After removing the duplicate dot, it worked again. Could you try this?
Regarding picking list for geo: I hear you. While doing my changes, I noticed that @TomekMelissa seems to have started adding support for this, see https://github.com/microsoft/2LCS/blob/4914fbd91d25cc432378a818ab056b74cfe8d2f7/2LCS/Enumerations.cs#L54
Would love to make this more user friendly, but that will take some time.

If you like I can invite you to a project so you have some were to test

That would be awesome, thank you!

@flauest This is now part of version 0.41.0.
@TomekMelissa I took the liberty of merging #76 and creating a new version with release notes. If nothing comes up until next week, I suggest we remove the prerelease flag and make it the latest version.


feat: Remove unnecessary dataset id references

This PR removes unnecessary use of the dsp:dataset attribute from the ContractOfferMessage and ContractRequestMessage but leaves it in the CatalogRequestMessage. For the former messages, the ODRL policy target attribute is used and the restriction to not allow that attribute in policies has been removed.
A new restriction is introduced to not allow target attributes on policy constraints as it does not make sense in our context but is permitted in ODRL.
Related Issues
Closes #192

To my understanding this would introduce a redundant dataset id in the catalog, correct? 1 in the dataset itself and 1 in the enclosed offer->target

To my understanding this would introduce a redundant dataset id in the catalog, correct? 1 in the dataset itself and 1 in the enclosed offer->target

yes, but that will avoid additional fields in the messages to specify the dataset: the offer will be self-contained and already able to tell to what dataset it's referring to. Same will be with the agreement.
Furthermore, not putting the target in the policy will be a violation of:

A Permission MUST have one target property value of type Asset. (Other relation sub-properties MAY be used.)
A Prohibition MUST have one target property value of type Asset. (Other relation sub-properties MAY be used.)

defining target at a root level is a way to tell "every rule has this target": https://www.w3.org/TR/odrl-model/#composition-compact

To my understanding this would introduce a redundant dataset id in the catalog, correct? 1 in the dataset itself and 1 in the enclosed offer->target

It would remove the redundant dataset property in the ContractOfferMessage and ContractRequestMessage. It would add the target attribute back to an Offer which must match the enclosing dataset id. This would make the Offer symmetrical with other policies. However, it would still allow referencing policies by URI and adding a target (so the referenced policy can be used generically):
"hasPolicy": {
   "@type": "Policy",
   "@id": "https://test.com/some-policy.json",
   "@target": "datasetid"
}

Also the https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/model/model.md file needs to be updated

I don't see where it needs to be updated beyond the changes I made in the PR. Did I miss something?

Also the https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/model/model.md file needs to be updated

I don't see where it needs to be updated beyond the changes I made in the PR. Did I miss something?

https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/model/model.md?plain=1#L70

Also the https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/model/model.md file needs to be updated

I don't see where it needs to be updated beyond the changes I made in the PR. Did I miss something?

https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/model/model.md?plain=1#L70

Isn't that changed in the PR?
https://github.com/International-Data-Spaces-Association/ids-specification/pull/193/files#diff-759257c54564e8398e104d8ac97c57863a742dd341e12a45a9e8e492475b7398

oh right, I overlooked that, sorry

Please do not merge yet. We need to discuss this further, e.g. my comment in the original issu:
https://github.com/International-Data-Spaces-Association/ids-specification/issues/192#issuecomment-1885135591

@jimmarino please revise/ turn back to old status as discussed


fix: navigator pop when using modal-barrier widgets

Pass modal widgets context (dialogs/bottom-sheets) to the pop method to not close the page that contains dropdown search instead.
Remove pop for dispose() because it's not safe to access context in dispose method, and it's not needed

Will fix this https://github.com/salim-lachdhaf/dropdown_search/issues/702

Is your fix did not impact this solved issue
https://github.com/salim-lachdhaf/dropdown_search/issues/554 ?

Hi, I have a similar issue and the PR https://github.com/salim-lachdhaf/dropdown_search/pull/712 also fixes it for me. @salim-lachdhaf could you please approve it?

issue fixed in 7.0.0-pre in another way.


README Bug Fix

The README file merged with the main branch had two bugs:

The .png file was not readable.
The alt text was not set.

Solutions:

The .png file is moved to the .images folder for accurate reference.
The alt text has been added as "screenshot".

The alt text has been updated on the push request, but the .png file is not yet associated with the specified file path. The 'images' folder remains to be created.

The images folder had been updated.


[ Feature Request ] Keyring support

I haven't acutally used to cli yet, but reading through it the plain text credentials bare some concern to me. As a future feature request it would be great if the credentials could be stored in a keyring (be it kde, gnome, or mac etc.), and then have the cli prompt for the credentials on first use.
Also, love the work you guys are doing here!

Hi David,
Thank you for this suggestion! It's an excellent feature and we really should add it to help people get rid of their plaintext credentials.
As for implementation, using a library with multi-OS support is kind of needed, perhaps either 99designs/keyring or zalando/go-keyring?


Analysis: Block.get_design_matrix not grouping by run level

The following bug is coming up when using fitlins on the generic_object_decoding dataset on OpenNeuro. (cc: @effigies )
I'm attempting to fit the following model.
{
  "name": "test_god_simple",
  "input": {
    "task": "perception",
    "run": "1"
  },
  "blocks": [
    {
      "level": "run",
      "model": {
        "variables": [
          "response_time"
        ],
        "HRF_variables": [
          "response_time"
        ]
      }
    }
  ],
  "description": "Simple GOD"
}

fitlins does something like following to set up the model:
analysis = Analysis(model='/analysis/model_orig.json',
                       layout=BIDSLayout(['/datasets/generic_object_decoding/'])
analysis.setup(**analysis.model['input'])

The problem comes when trying to get the design matrices in the first 'run' block (in the first_model function of fitlins). Presumably, the following line should return a list of design matrices and entities for every run that matches "input":
dms = analysis[0].get_design_matrix(analysis[0].model['HRF_variables'], mode='sparse')

This returns 40 design matrices, only for run=1, but the entity run is not listed among the entities. For example, the entities for dms[0] = {'session': 'perceptionTest01', 'subject': '01', 'task': 'perception'}
This causes an error in fitlins because preproc files are not subsequently filtered correctly.
Confusing, if I change the json model to omit run from input, I get a similar result from get_design_matrix with 40 design matrices being return. But now, the design matrix dataframes include events for all runs (10 in this case). I would have expected a design matrix per run, even if I was not filtering on runs. In this case, entities also does not include run as a key.
Any ideas? Am I correct in thinking get_design_matrix should always return a result for each run individually?
I'll do more digging and see if I can replicate this result on another dataset

I'm not able to look at this just now, but one thought is that IIRC, get_design_matrix doesn't return a run entity value if run is not explicitly included in the filename. So that might be the issue. But I think there was a good reason for doing it that way, so I wouldn't call this a bug (though we might need a workaround here). If that's not the problem, then I'm not sure...

Oh and you're right that you should always be getting a single run per list element. Will look into that when I can if Chris doesn't figure it out first.

In this dataset, run values are explicitly in the filenames, and the it passes BIDS validaton: https://openneuro.org/datasets/ds001246/versions/00002?app=FMRIPREP&version=54&job=5ab2f56ed5151800014bcc3a

Okay I've found the bug. It is happening in kollekshuns.BIDSVariableCollection._index_entities
That function omits entities if they vary across the collection. It turns out run was being represented as both a string and an integer within a set of variables. Specifically, SparseRunVariables represented run as an int, and DenseRunVariables as a string.
This commission then propagated all the way down, and caused the issues I outlined above. In the case of a more than one type of run, it caused incorrect grouping of variables at higher levels (grouping them together, rather than one per run).
Seems as they should be a string in both correct?

Ah, thanks, that makes sense. They should actually all be integers; the spec requires run values to be ints. What's not clear is why they're being assigned as strings; can you track that down? In grabbit, the run entity now has type int, and conversions to int should be internally forced when first reading the files in, so this shouldn't be happening at all.

It's actually coming from BIDSVariable._index_entities. In the case of a Dense variable, it uses the index to build a list of entities:
https://github.com/INCF/pybids/blob/d481dda98c7e3b38b4a812124daaf0d450d64e19/bids/variables/variables.py#L210
self.entities = {k: self.index[k].iloc[0] for k in keep}

The dtype for self.index['run'] is object, so its coming out as a string rather than an integer.
I'll track down a bit further, but I'm guessing making sure the dtype is int when building the DenseIndex should fix the issue.

https://github.com/INCF/pybids/blob/d481dda98c7e3b38b4a812124daaf0d450d64e19/bids/variables/variables.py#L401
np.broadcast_to seems to return all dtype='object' rather than respecting the incoming dtype


Cannot read properties of undefined (reading 'platform')

What happened?
Hi, i have just integrated the rnx bundler into my app but when i run bundler using  react-native rnx-start command i get the following error :
Cannot read properties of undefined (reading 'platform')
at Object.hook [as experimentalSerializerHook] (/Users/.../node_modules/@rnx-kit/cli/lib/metro-config.js:25:49)
Affected Package
@rnx-kit/cli
Version
0.14.0
Which platforms are you seeing this issue on?

[X] Android
[X] iOS
[ ] macOS
[ ] Windows

System Information
System:
    OS: macOS 12.2
    CPU: (8) arm64 Apple M1
    Memory: 169.45 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.14.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.3.1 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
    Android SDK:
      API Levels: 23, 28, 29, 30, 31, 32
      Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0
      System Images: android-32 | Google APIs ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.1 AI-211.7628.21.2111.8193401
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.2 => 0.64.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to Reproduce
just integrating to an existing app
Code of Conduct

[X] I agree to follow this project's Code of Conduct

setting "typescriptValidation": false, in package.json solved the issue

@afoxman, do we need to provide a better error message here? Or not enable typescriptValidation in this scenario?

@afoxman, do we need to provide a better error message here? Or not enable typescriptValidation in this scenario?

I'm guessing this is because of react-native: 0.64.2, which is using Metro < 0.66 which has the serializer-hook fix (adds transformOptions). And so this line is imploding:
const platform = graph.transformOptions.platform as AllPlatforms;
Yes, we should have a more graceful "you are using an unsupported version of Metro" message and then just ignore typescript validation entirely.


Mod is unavailable on Third-party Launchers

You have the Curseforge "Prevent Third-Party Distribution" setting enabled, which prevents your mod from being used on third-party launchers. Many people do not want to use the Overwolf launcher due to privacy and data-harvesting concerns, or inaccessibility on Linux, and this restriction makes it difficult for those people to use modpacks with your mod in them, as well as discouraging pack developers from including your mod. Additionally, it makes it much more difficult to host a server with this mod. For more details, see https://gist.github.com/copygirl/7d45bad739453d2be61138cebafce04c
I'm assuming this is unintentional since your mod is under the MIT License and available on Modrinth.

I forgot this option. Now you can!


Added some new commands

I added a new "launch" command, trimmed out some extra "using" statements, and added aliases for all commands. I wanted to contribute this to your code, because you are the original developer. If you don't want this contribution, I'll upload my own private version. Check the individual commit notes for more info!

Thanks!


Readme: Setup allow copy paste of npm install

At least in my bash shell when copy pasting the npm install ... it's running a full install and complains that all the libs are no bash commands.

Coverage remained the same at 100.0% when pulling 638eef7fea4adf4ebd3120519d14193086105c91 on karfau:patch-1 into 5bd0505a36df73b2bd568c8eec14b9f4b0a9ada0 on styled-components:master.


Backslash being removed from name variable when used with use_fullname

Though I think this is by design rather than a bug, it should be discussed.
Describe the Bug
Slashes are removed from the name variable even when use_fullname is true
Expected Behavior
Characters valid for the service should be valid for the module. Whilst regex_replace_chars does a good job of keeping the most valid characters, another regex var is required for when name is used alongside a use_fullname=true. We should be overriding regex_replace_chars as it has a wider impact than just the name variable.
Maybe even take this a step further and use the namespace before adding a slash when use_fullname=false?
Steps to Reproduce
Apply the module with a name that contains a / and use_fullname=true, the slash will not be in the name of the ECR repository.

Sorry, one should RTFM properly. My Bad.


Remove unused code

Fixes #2311.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.1%) to 87.077%

Totals

Change from base Build<PHONE_NUMBER>7:
1.1%

Covered Lines:
1388

Relevant Lines:
1594

💛  - Coveralls


ISPN-7512 Add FRAG3 back to TCP configuration

https://issues.jboss.org/browse/ISPN-7512

👍 💯 🥇 from me!

👍 Seems good to me, but I would wait to see what @danberindei says.  I don't understand how it would work with a bigger message (larger than credit size) without FRAG.

@pruivo Just a silly question, shouldn't we run perf tests here?

@slaskawi When the difference is between working and not-working, I'm not sure perf tests are relevant... either way, our perf tests use 10k values, so they would never be fragmented (the default frag_size is 60k).
I'd make frag_size even bigger, say 200k, to make fragmentation even less likely. For reference, max_credits * min_threshold is 800k in our default configs.

updated the frag_size except for server configuration that uses jgroups-defaults.xml values.

Aha, server does not have a way to distinguish between defaults for TCP and for UDP.

@tristantarrant added the explicit frag_size to that 2 places

Merged, thanks


Logs

Sorry, I can't merge this pull request. There are several problems with it:

Pull requests shouldn't be sent to 'master' branch (See [CONTRIBUTING.md])(https://github.com/codinguser/gnucash-android/blob/master/.github/CONTRIBUTING.md)
It mixes unrelated changes. Code refactors in the first commits with changes in the definition of log tags in the later ones.
Changes like the ones in the first commits should be avoided. It's better to do so in the way to fixing some bug or adding some feature.
Commit messages should describe the change properly, be atomic... See, these guidelines for example.

Apart from this, it's better to start contributing to a project by working on some small issue from the bug tracker or that you might have found.


Roll engine 0d83a2ecd1bb..3a3f707d5a9b (25 commits)

https://github.com/flutter/engine/compare/0d83a2ecd1bb...3a3f707d5a9b
git log 0d83a2ecd1bb78f8e1f0ed9719ff3751cdfdd064..3a3f707d5a9b17388b60ff10b9f65b0c6a3c4134 --no-merges --oneline
3a3f707d5 Reland "Allow specification of std::functions as native entrypoints from Dart code." (flutter/engine#8329)
d4275d9ee Roll src/third_party/skia 576eb87a2d2d..99ccc0ca87e6 (5 commits) (flutter/engine#8328)
3a415c4f1 Map glfw into third_party, and roll buildroot (flutter/engine#8308)
ce9ea5869 [fuchsia] Disable FML_TRACE_COUNTER events to unblock roll (flutter/engine#8325)
48496588c Roll src/third_party/dart 8a92d2a8d9..991c9da720 (2 commits)
20c241ac3 Roll src/third_party/skia c476e5da4fef..576eb87a2d2d (7 commits) (flutter/engine#8324)
cadcf1c58 Roll src/third_party/dart f3fd1943fc..8a92d2a8d9 (16 commits)
66141eb8e Roll src/third_party/skia d1c271bd39f0..c476e5da4fef (2 commits) (flutter/engine#8322)
e5b31cdd9 Roll src/third_party/skia cec20280b3fb..d1c271bd39f0 (3 commits) (flutter/engine#8321)
1daff5ce1 Roll src/third_party/skia bf341ae88c83..cec20280b3fb (3 commits) (flutter/engine#8320)
87db585ad Roll src/third_party/skia 45d5f702133e..bf341ae88c83 (2 commits) (flutter/engine#8316)
fd7d7fa5a Add a11y support for embedded iOS platform view (flutter/engine#8156)
f64ee01e1 Roll src/third_party/skia d2ca31218bc4..45d5f702133e (11 commits) (flutter/engine#8315)
f521df383 Fixed service isolate not being initialized correctly due to bad name (flutter/engine#8251)
80b825ce8 Roll src/third_party/dart 093c2909fe..f3fd1943fc (13 commits) (flutter/engine#8310)
7e77d5c48 Revert "Allow specification of std::functions as native entrypoints from Dart code. (#8309)" (flutter/engine#8312)
400a86a62 Allow specification of std::functions as native entrypoints from Dart code. (flutter/engine#8309)
51f23fedf [vulkan] Add FUCHSIA external sem/mem extensions
78de8dcb4 Enable lambda like native callbacks in tests and add support for custom entrypoints. (flutter/engine#8299)
2812c7db4 Roll src/third_party/skia 62fd6c411622..d2ca31218bc4 (9 commits) (flutter/engine#8307)
95f9134e9 Roll src/third_party/skia d90004516a63..62fd6c411622 (4 commits) (flutter/engine#8306)
358273bd2 Roll src/third_party/skia 33211b2c7a02..d90004516a63 (1 commits) (flutter/engine#8305)
2804057bf Roll src/third_party/skia 80dd599e91d0..33211b2c7a02 (1 commits) (flutter/engine#8303)
a673bbf6f Roll src/third_party/skia c5ee499f2c59..80dd599e91d0 (5 commits) (flutter/engine#8301)
d88037dc0 Roll src/third_party/dart fa74184b7a..093c2909fe (71 commits)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (bmparr@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


alt_text missing

Hello, I'm using tweepy 3.10 and I need to check whether a tweet contains images or not, and in case that images are included, if alt_text is given too.
However, I found some tweets does contain image and alt_text but doesn't I can't get it with the API.
Consider this twet: I get it with the following line:
status = api.get_status(tweet_id, include_ext_alt_text=True, include_entities=True)

But status object does not contain extended_entities attribute, so I can't go to status.extended_entities['media'][0]['ext_alt_text'] to get alt_text. Notice that this work for some other cases like this.
Any ideas? my full code is here if you want to check it, any help is appreciated.
thanks!

You'll want to use extended tweet_mode.
See the section in the documentation about extended Tweets.


Make key and serialization optional in /logs requests.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1526  👈 (View in Graphite)
#1525
#1468
#1439 : 1 other dependent PR (#1440 )
#1364
#1362
#1361
#1360
#1314
#1347
#1433
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 5, 1:25 PM EST: A user started a stack merge that includes this pull request via Graphite.


Book Section

Description
As of now the cards when hover , size is increasing but not proper manner , not in standard mannner. It is also not user-friendly interface. I can fixed this
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
Safari
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

I have fixed this issue , please check PR and merge it

PR has been merged successfully by admin


app.js file not opening

Downloaded the starter code, and opened folder in Sublime Text. App.js file won't open, and isn't even clickable in the folder tree.

Hi!
Thanks for the feedback. I've rewritten the codelab from scratch and believe I have fixed this issue. The code has been updated, and the new guide is now live.
If you find any issues with the new codelab, please let us know!
Thanks!


⚠ Turnos 24x7 has degraded performance

In 8310766, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 993 ms

Resolved: Turnos 24x7 performance has improved in ed964a0.


ImportError: cannot import name 'UniformGrid' from 'pyvista'

If you encounter this error, use conda to downgrade the pyvista version to 0.38
conda install pyvista=0.38
It seems that "UniformGrid" function was removed from the latest version of pyvista.

Hi @Biogod2020, thank you very much for raising this issue and providing a solution. In fact, we develop spateo based on version 0.38.0 of pyvista, so this problem may exist. In the future we will update a new version of spateo to support all the latest versions of basic dependency packages.


refactor: Join-split example Part 1

The first of a two-part series to refactor the join-split example, the goal being to focus the tests on circuit writing (no proof construction), update them to reflect our newer idioms, and relocate them.  Key changes

Keep a subset of tests relating to circuit writing.
Remove code that has to do with proof construction.
Add a new circuit change detection paradigm: rather than hashing a verification key (a proving system-dependent object), simply hash the circuit-defining data in the circuit builder.
Delete unused code (some unused before, some unused now).

The next PR https://github.com/AztecProtocol/aztec-packages/pull/5016 will move and condense files, and update namespaces.

@lucasxia01 made an issue to follow up on a particular question: https://github.com/AztecProtocol/barretenberg/issues/900


Missing QueryBreakdown in EXPLAIN ANALYZE with composite PK on partitioned table

CrateDB version
5.4.3 and crate/crate:nightly-5.5.0-2023-10-11-0
CrateDB setup information
discovery.type=single-node
Problem description
It seems EXPLAIN ANALYZE is not returning a detailed plan for certain queries.
Steps to Reproduce
CREATE table tbl1 (a INT PRIMARY KEY,b int);
EXPLAIN ANALYZE SELECT * FROM tbl1 WHERE a BETWEEN 0 AND 4;
--> range lookup on PK results on QueryBreakdown

CREATE table tbl2 (a INT,b int,c int, PRIMARY KEY(a,b));
EXPLAIN ANALYZE SELECT * FROM tbl2 WHERE a  BETWEEN 0 AND 4 AND b BETWEEN 0 AND 4;
--> range lookup on components of composite PK results on QueryBreakdown

CREATE table tbl3 (a INT,b int,c int, PRIMARY KEY(a,b)) PARTITIONED BY (a);
EXPLAIN ANALYZE SELECT * FROM tbl3 WHERE a  BETWEEN 0 AND 4 AND b BETWEEN 0 AND 4;

Actual Result
no QueryBreakdown?
Expected Result
A detailed QueryBreakdown

You need to insert at least one value, so that at least one partition is created and then you get the explain analyze, otherwise there is no actual table created internally (only a template):
insert into tbl3(a, b, c) values(1, 11, 111);
cr> EXPLAIN ANALYZE SELECT * FROM tbl3 WHERE a  BETWEEN 0 AND 4 AND b BETWEEN 0 AND 4;
...
...
                    "create_weight_count": 1.0,
                    "build_scorer": 0.0
                  },
                  "QueryName": "IndexOrDocValuesQuery"
                }
              ],
              "QueryName": "BooleanQuery"
            }
          ]
        }
      },
      "Plan": 0.289335,
      "Analyze": 0.514658
    }
  }
]

I think we could add a note to the docs about that, so that users are not surprised, could you take care of this @hlcianfagna ?


[FLINK-3738] [tableAPI] Refactor TableEnvironments. Remove Translators and TranslationContext.

[x] General

The pull request references the related JIRA issue
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message

[X] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[X] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

Removes Translators (JavaBatchTranslator, ScalaBatchTranslator, JavaStreamTranslator, ScalaStreamTranslator)

Removes TranslationContext

Creates TableEnvironments for Java/Scala DataSet/DataStream APIs

Functionality of translators and translation context is moved to table environments

Tables are bound to a TableEnvironment

Simplifies table translation from and to DataSet / DataStream.

Updates documentation and cleaned up ScalaDocs

Thanks for the massive refactoring @fhueske!
I looked over the changes and couldn't spot anything noteworthy. The only things that I don't like is the additional TableEnvironment creattion even for simple table programs when using implicit conversions. Couldn't we just also provide a static TableEnvironment if we call the parameterless toTable that just calls (Stream)ExecutionEnvironment.getExecutionEnvironment()?

I thought about that as well, but decided against an implicit conversion without TableEnvironment.
What might happen otherwise is that users try to join or union tables that have different implicitly created TableEnvironments or to register an implicitly converted table in a TableEnvironment. This does not work due to Calcite internals. I think it is better to make the Table/TableEnvironment relationship explicit and also easier to understand for users if an exception is thrown for the above reason.

Just a couple of typos from my side.
I really like it that we got rid of the TranslationContext and I'm in favor of the explicit relationship between Tables and TableEnvironment. +1 to merge!

Thanks for the review @vasia.
I fixed the typos.

will merge this.


Count 'n' must be non-negative, but was -2.

Description
After upgraded the apollo version from 1.0 to 2.1, built the app and it showed "Count 'n' must be non-negative, but was -2." error message. It is related to GraphQLDocumentSourceBuilder.kt line 93 string with indents problem.

I don't know which query caused the issue. May be I can give you one sample.
query ArticleListQuery($name: String!, $limit: Int!, $offset: Int!, $excludeEntityIds: [String]!) {
    queue(filter: {name:$name}){
        entityId
        entityUuid
        name
        items(limit: $limit, offset: $offset, exclude: {entityIds: $excludeEntityIds}) {
            ... on Article {
                ...ArticleLite
            }
            ... on Video {
                ...VideoLite
            }
        }
    }
}

hi @wooyukit sorry for the delay, but we couldn't reproduce this issue on provided sample.
Is it still a valid issue?

I put a potential fix, but TBH if you see this issue looks like your GraphQL query is no valid.

There is a workaround for this in 2.x and 3.x uses a SDLWriter to avoid this.


🐞 forgot to bump appVersion 🐞

What is this PR About?
I forgot to bump the appVersion in https://github.com/redhat-cop/helm-charts/pull/177
should be 2.0.5
How do we test this?
Provide commands/steps to test this PR.
cc: @redhat-cop/day-in-the-life

/lgtm
/approve


1.2.0 tries to download a file from gitlab and fails

As reported on discord.
https://discord.com/channels/436568060288172042/1138448122968813578

Links with redirects not supported by the installer:

[ ] https://gitlab.com/api/v4/projects/diskuv-ocaml%2Fdistributions%2Fdkml/packages/generic/ocaml_opam_repo-reproducible/1.2.0/ocaml-opam-repo-4.14.0.zip
[ ] More to come ... testing 1.2.0 in Windows Sandbox
[ ] More to come ... testing 2.0.2 (preview) in Windows Sandbox

Tools to fix:
docurl() { curl --header "PRIVATE-TOKEN: ..." "$@"; }

doput() { _f=$1; shift; _d=$(dirname "$_f"); install -d "$_d"; docurl "https://gitlab.com/api/v4/projects/dkml%2Fdistr
ibutions%2Fdkml/packages/generic/$_f" > "$_f"; file "$_f"; docurl --upload-file "$_f" "https://gitlab.com/api/v4/project
s/diskuv-ocaml%2Fdistributions%2Fdkml/packages/generic/$_f"; }

doput ocaml_opam_repo-reproducible/1.2.0/ocaml-opam-repo-4.14.0.zip

Thanks for reporting the issue!


[ksp] No providers found in processor classpath.

Anybody knows how to solve this issue  ?

I forget to add:
dependencies {
ksp("io.mcarle:konvert:$konvertVersion")
}
I had "[ksp] No providers found in processor classpath." error with mapstruct so I thought that this library is broken too, but after adding ksp("io.mcarle:konvert:$konvertVersion") it works


Attempt to INSERT object with nested reference data children fails with InvalidOperationException

In our case we've got types referencing eachother like this: UserDto > PhoneNumberDto > CountryDto > CurrencyCodeDto.
PhoneNumberDto isn't reference data, but is treated as such because the relevant properties on UserDto are marked as reference data, like so:
[Column("OfficeNumberKey")]
[OneToOne]
[ForeignKeyReference(typeof(PhoneNumberDto)]
[ReferenceData]
public PhoneNumberDto OfficeNumber { get; set; }

CountryDto and CurrencyCodeDto are both reference data and marked as such at the type level with [ReferenceData] attribute decorations.
The problem occurs when you try to INSERT a UserDto. Now SimpleSave 1.0.65 correctly skips the PhoneNumberDto but, of course, it's continued to diff all the way down beyond that, so generates an UpdateOperation, which gets caught later as invalid, and leads to the following error:
System.InvalidOperationException : You cannot perform UPDATEs on a reference data table with no updateable foreign keys. Attempt was made to UPDATE table [gen].[COUNTRY_ENUM], column CurrencyCodeKey.
  at Dapper.SimpleSave.Impl.CommandBuilder.ValidateUpdateOperation(UpdateOperation update)
  at Dapper.SimpleSave.Impl.CommandBuilder.Coalesce(IEnumerable`1 operations)
  at Dapper.SimpleSave.Impl.TransactionBuilder.BuildUpdateScripts(T oldObject, T newObject, Boolean softDelete)
  at Dapper.SimpleSave.SimpleSaveExtensions.UpdateInternal(IDbConnection connection, IEnumerable`1 oldAndNewObjects, Boolean softDelete, IDbTransaction transaction)
  at Dapper.SimpleSave.SimpleSaveExtensions.UpdateAll(IDbConnection connection, IEnumerable`1 oldAndNewObjects, IDbTransaction transaction)
  at Dapper.SimpleSave.SimpleSaveExtensions.Update(IDbConnection connection, T oldObject, T newObject, IDbTransaction transaction)
  at PS.Mothership.Domain.UserManagement.UserRepositoryV2.SaveUserInternal(IDbConnection connection, UserDto oldUser, UserDto newUser, IUserInputFilter[] filters) in UserRepositoryV2.cs: line 183
  at PS.Mothership.Domain.UserManagement.UserRepositoryV2.<>c__DisplayClassa.<SaveUser>b__8(IDbConnection connection) in UserRepositoryV2.cs: line 167
  at PS.Mothership.Repository.Implementations.BaseCustomQueryDapperRepository.Execute(Func`2 work) in BaseCustomQueryDapperRepository.cs: line 21
  at PS.Mothership.Domain.UserManagement.UserRepositoryV2.SaveUser(UserDto oldVersionOfUser, UserDto newVersionOfUser, IUserInputFilter[] filters) in UserRepositoryV2.cs: line 167
  at PS.Mothership.Domain.UserManagement.HrUserUpdateService.Update(LegacyHrUpdateUserDto hrUser) in HrUserUpdateService.cs: line 105
  at PS.Mothership.IntegrationTest.HumanResources.HrIntegrationUserTests.hr_can_create_and_update_user() in HrIntegrationUserTests.cs: line 109

It's good that the problem is caught and the error thrown, but the fact remains that operations for tables that are children of the initial reference data table should not be generated.
This actually needs to be fixed at the diff level, before we start generating operations because, by that point, the hierarchy information isn't available in an easy to digest form.

This is really weird. I've spent a bit of time trying to reproduce this, even going to the extent of copying the exact object definitions that fail in PS and duplicating them in the test case, and it fails, but for a different reason. Rather than in the script generation, which is where I'd expect it to break, it's failing (predictably) when it tries to execute the SQL because we don't have a real, open connection to a database.
I'm quite certain I know how to fix it but I don't want to go ahead and do that, ideally, without a test in place that demonstrates it's now fixed.

This appears to be fixed but it would still be nice to have a test that reproduces it and protects against regression.


[6.0] Much faster navigator index creation for mixed Swift and Objective-C projects

Explanation:
This significantly improves the build time for large (10k+ symbols) mixed Swift and Objective-C projects; about 5 times faster total docc convert time. It does so by fixing a major bottleneck in the creation of the navigator index.
Scope: Navigator index creation for mixed Swift and Objective-C projects
Issue: rdar://127759734
Risk: Low
Testing: New tests verify that both the fast and slow code paths produce the same navigator index for mixed Swift and Objective-C projects with refined symbol hierarchies. All existing navigator index tests pass.
Reviewer: @mayaepps
Original PR: #917

Note:
Some new code depended on the ability to sort source languages which was an underlying change in #856 but which was never cherry-picked over to the 6.0 release. I brought over only that change in https://github.com/apple/swift-docc/pull/924/commits/64440369b494e5d00f10bead12a613e28705be61.

@swift-ci please test

@swift-ci please test


Input method doesn't support any styles with specific wm

Tested versions

Reproducible in 4.1.3 stable, 4.2.1 stable and 3.5.2

System information
NixOS - Godot 4.2.1 - exwm - ryzen 5600x - rx6800xt
Issue description
When trying to start godot4, it throws
Godot Engine v4.2.1.stable.nixpkgs.b09f793f5 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Xshape 1.1 detected.
Xinerama 1.1 detected.
Xrandr 1.6 detected.
Xrender 0.11 detected.
Xinput 2.2 detected.
XInput: Refreshing devices.
XInput: No touch devices found.
Input method doesn't support any styles
free(): invalid pointer
[1]    150537 IOT instruction (core dumped)  godot4 --verbose

But only when using exwm, I tryied awesomewm, xfce, lxde and all of them work, therefore I'm not sure if this is a godot issue or exwm issue, I'm sorry if I should be asking in another place.
I tried the solution in #42101 (DRI_PRIME=0) but it didn't work.
This is the output in awesomewm:
Godot Engine v4.2.1.stable.nixpkgs.b09f793f5 - https://godotengine.org
WARNING: XOpenIM failed
     at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:5951)
WARNING: XCreateIC couldn't create wd.xic
     at: _create_window (platform/linuxbsd/x11/display_server_x11.cpp:5575)
OpenGL API 4.6 (Core Profile) Mesa 23.1.9 - Compatibility - Using Device: AMD - AMD Radeon RX 6800 XT (navi21, LLVM 16.0.6, DRM 3.49, 6.1.72)

Steps to reproduce

Start godot

Minimal reproduction project (MRP)
N/A

Update:
I broke my system, and since I had a couple of other problems with nixOS, I switched to arch. In arch, using the same setup for exwm, it worked perfectly, so I suppose it's not an exwm issue but a nixOS one (or both?).
So I'll mark this as closed.

I could reproduce the "bug". It was related to XIM and exwm-xim. Running godot with XMODIFIERS="" works, just without exwm-xim, obviously. I am not sure if this is a godot issue or an exwm issue.


Silence on all iterations

Hello.
I'm currently training wavegan-pytorch with a set of files (<300) and I'm getting silence files every iteration - it generates 10 .wav but it's silence, 0 values all duration. During the installation, I had some problems with librosa in my machine and changed line 172 on utils.py to:
    #librosa.output.write_wav(output_path, sample, sampling_rate)
    sf.write(output_path, sample, sampling_rate) #'PCM_24')

sf as of soundfile library. Might this be the problem? Is there a script here to navigate the latent space and debug this?
Thanks in advance.
Luis

your solution might have felt into local optima . This has happened to me while training . But still i am trying to get the proper drum sound but getting very different sound after 150 epoch not even similar to drum just big  booms

What does that mean? The problem is not writing files, the thing is that they are all silent. I do 200 epochs and it is always silent, except for the 0 folder which are an inaudible noise with very little amplitude.

Introduce momentum in the optimizer that might help u to escape local minima

That's a good point. @ALI7861111 do you have any example/fork that I can look at/use?

@luisArandas did you ever resolve this? This is happening to me as well.


Expose service_binding_state metrics

Update the docs for to reflect the exposed binding metrics.
Sample prometheus query output for "interoperator_service_bindings_state":
interoperator_service_bindings_state{app_kubernetes_io_managed_by="Helm", binding_id="0abc2107-de86-408d-8617-800935b84028", control_plane="interoperator-multiclusterdeployer-controller-manager", instance="<IP_ADDRESS>:8443", instance_id="80ca2362b-6561-4673-ad24-111d7ac86cfd", job="kubernetes-service-endpoints", kubernetes_name="interoperator-multiclusterdeployer-metrics-service", kubernetes_namespace="interoperator", kubernetes_node="shoot--interop--pooja-dev-worker-j5mor-z1-6b645-p2xjs"}

Validation on k8s cluster: n-1 is succeeded.

The sample dashboards look like the following:

Pull Request Test Coverage Report for Build 5468

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.78%

Totals

Change from base Build 5465:
0.0%

Covered Lines:
9708

Relevant Lines:
10557

💛  - Coveralls

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n+n+n is succeeded.


[DCOS-45166] Add a file which separates tests into groups

High-level description
This introduces a new file that developers must interact with, test_groups.yaml.
It must specify pytest patterns which cover all tests.
We have a test which confirms that it does this.
We have a TeamCity job which proves that this works.
See here.
This is based on a template we created.
Let's merge this PR, then create four new TeamCity jobs from the templates.
Then we can stop running the existing TeamCity job.
Once this has a Ship It (and therefore the API is accepted), we will start on the TeamCity task of turning our PoC into a job which runs on all PRs and reports to GitHub.
We will also start on the Enterprise equivalent and setting up the AWS integration tests to do the same.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-45166 Parallelize Integration Tests - docker
DCOS-45164 Parallelize Integration Tests - ec2

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: This is a test-only change
[X] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[X] Read the DC/OS contributing guidelines

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

When the proposed TeamCity changes are made, branches which are not up to date will run all tests x 4:
[04:31:03]W:	 [Step 5/7] ++ ./dcos-docker run --cluster-id build-30 python open_source_tests/get_test_group.py group_1
[04:31:05]W:	 [Step 5/7] python: can't open file 'open_source_tests/get_test_group.py': [Errno 2] No such file or directory
[04:31:06]W:	 [Step 5/7] + TEST_NAMES=
[04:31:06]W:	 [Step 5/7] + ./dcos-docker run DIAGNOSTICS_DIRECTORY=1 --cluster-id build-30 DCOS_REGISTRY_S3_AWS_ACCESS_KEY_ID=******* DCOS_REGISTRY_S3_AWS_SECRET_ACCESS_KEY=******* DCOS_REGISTRY_S3_ENDPOINT=s3-us-west-2.amazonaws.com DCOS_REGISTRY_S3_BUCKET=dcos-package-registry-test pytest --teamcity -vv -rs

@mesosphere-mergebot sync

Mergebot's ship it label thing seems to be not working.

@mesosphere-mergebot label ship it


feat: support richtext

Fixes #

Proposed Changes

...
...
...

Readiness Checklist
Author/Contributor

[x] If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

[x] Label as either enhancement, bug, documentation or dependencies
[x] Verify design and implementation

https://cloud.tencent.com/developer/ask/sof/127731
https://blog.csdn.net/paincupid/article/details/9336733


feat: adds http endpoints for ciraconfig, wireless config and 8021x c…

…onfig

Failing Tests

[ ] Get All CIRA Configs expect Not Modified
[ ] Edit CIRA Config returns Confilct
[ ] Edit CIRA Config returns Precondition
[ ] (Wireless) Create Profile


CM5 support

Is it possible to add CM5 support? pigpiod currently tells me it isn't a Raspberry Pi. I can help with any info you need by running commands on the cm5. This is waht /proc/cpuinfo says:
processor	: 0
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 1
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 2
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 3
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

Revision	: b04180
Serial		: 086b5fc3b16db98e
Model		: Raspberry Pi Compute Module 5 Rev 1.0

Sorry, Pi5/CM5 architecture has changed making  pigpio incompatible.   Do you have a recommended alternative?

Lgio

Hmm that's a Python API. I'm working from nodejs. I'll dig further.


MenuItemOptions click property incorrect

The MenuItemsOptions click property is incorrect.
The property has a function signature of:
MenuItem -> BrowserWindow -> KeyboardEvent -> unit
when it should be
unit -> unit
I was able to work around this by doing:
let mutable tray: Tray option = Option.None

[<Emit("$0")>]
let menuItemOptionsPojo menuItemOptions : MenuItemOptions = jsNative

let show =
    menuItemOptionsPojo
        ({| label = "Open"
            click =
                fun () ->
                    match mainWindow with
                    | Some(win) -> win.show()
                    | None -> () |})
    |> U2.Case1

let appTray =
    main.Tray.Create("")

main.Menu.buildFromTemplate [| show |]
|> Some
|> appTray.setContextMenu

tray <- Some appTray

Are you sure? The current signature is according to the Electron docs.

Yeah, that had me confused as well.
I looked around a lot on the web and never saw anyone set the click property to anything but unit -> unit. I just found one blog post published recently that used that function signature, but I never had any success with it. I usually did it like:
let show =
    menuItemOptionsPojo
        ({| label = "Open"
            click =
                fun (_, _, _) ->
                    match mainWindow with
                    | Some(win) -> win.show()
                    | None -> () |})
    |> U2.Case1

Which would never fire. At the very least I can confirm that it does accept unit -> unit. You can also see them do this in the official docs here.

Yes, AFAIK in JS you can drop arguments if you don't need them, so even if you have a callback signature like a -> b -> unit you can supply unit -> unit.
I suggest you post an issue in the Electron repo, to tell them about this possible bug in the docs. If it really is a bug I can fix the signature.
Come to think of it though... I had a similar issue recently where I explicitly had to wrap the callback in Func: https://github.com/Zaid-Ajaj/Feliz/issues/27
Could you try that with your callback? I.e., something like:
let show =
    ({| label = "Open"
            click =
                Func<_,_,_,_>(fun (_, _, _) ->
                    match mainWindow with
                    | Some(win) -> win.show()
                    | None -> ()) |}
    |> U2.Case1

Yeah it doesn't like that since it's expecting three arguments it treats the System.Func as a single argument of the three required. Unless I'm just doing it wrong. My repo is public if you want to look at it yourself.

Oh, right. Try "cheating" by unboxing the Func to the correct type: unbox(fun (_, ...

I was able to get this to work:
let show =
    main.MenuItem.Create
        (jsOptions<MenuItemOptions> (fun o ->
            o.label <- "Open"
            o.click <-
                unbox(System.Func<_,unit>(fun (_, _, _) ->
                    match mainWindow with
                    | Some(win) -> win.show()
                    | None -> ()
                )))
            )
    |> U2.Case2

Dang. That likely means that any multi-parameter callback in Fable.Electron suffers from the same problem.

@Zaid-Ajaj or @alfonsogarciacaro do you have any tips on how to write bindings like the below, considering that the code below doesn't work due to currying?
https://github.com/fable-compiler/fable-electron/blob/bcffb111efc02688d936a0c7b2ea80137ef2ba74/src/Fable.Electron/Bindings.fs#L7381

Seems like the "direct" solution is to create an alias U3<Func<MenuItem, BrowserWindow, KeyBoardEvent, unit>, Func<MenuItem, BrowserWindow, unit>, Func<MenuItem, unit>.
I know it looks harder to read but should solve the problem. Other solutions probably need something from the compiler itself I guess.

Will using Func force the user to use Func explicitly too, or is that handled automatically by F#/Fable?
Regarding U3: Given how hard the signature is to read (and the fact that the user must use U3.CaseX or !^), I think only the most general callback is better, and users can just use _ for the ignored parameters.

When you use jsOptions you limit yourself in how you initialize the properties and you cannot do "postprocessing" internally in the library to hide some ugly js parts. I guess the best way here is to use overloaded click handlers and then cast them to Func internally before making the property.
I haven't tested the code below but it goes something like this
type IMenuItemProperty = interface end

type MenuItem with
    static member click (handler: MenuItem -> BrowserWindow -> KeyboardEvent -> unit) : IMenuItemProperty  =
      !!("click", System.Func<_, _, _, _> handler)
    static member click (handler: MenuItem -> BrowserWindow -> unit) : IMenuItemProperty  =
      !!("click", System.Func<_, _, _> handler)
    static member create (props: IMenuItemProperty list) = main.MenuItem.Create (!!createObj (!!props))

main.MenuItem.create [
   MenuItem.label "show"
   MenuItem.click (fun item window keyboardEvent -> ())
   MenuItem.click (fun item window -> ())
   MenuItem.click (fun item -> ())
]

Of course this property list syntax doesn't always make sense but in case of UI elements (menu items in this case) it would work nicely

Thanks! Yes, the Electron bindings are currently "very JS".
General note: Suggestions for improvements, and PRs, are welcome! I have very limited capacity at the moment to work on significant changes to this library. Therefore, at the moment, I'm just looking for a quick fix to actually make this work (and for similar other multi-parameter function properties).

Therefore, at the moment, I'm just looking for a quick fix to actually make this work

To test but then perhaps:
abstract click: Func<MenuItem, BrowserWindow, KeyboardEvent, unit> with get, set

Force the user to provide a Func<> construct.

Come to think of it, would that just be Action<MenuItem, BrowserWindow, KeyboardEvent>?

@Shmew 3.0.0 will be published soon. Please let me know if it's fixed.

I agree with you @cmeeren my position in general is to have a pure bindings.
And if people needs something more high level, we (or the consumer) can either have an Helpers module or a dedicated package for that.