go: malformed module path "function/faas": missing dot in first path element

[Vishal1297]

I'm new in Knative, and trying to run golang hello kn func example on my local.

After running the build command, I am getting a weird error - go: malformed module path "function/faas": missing dot in first path element

ENV

➜  kn-hello-func git:(main) ✗ kn version
Version:      v1.13.0
Build Date:   2024-01-24 16:48:59
Git Revision: 543522a3
Supported APIs:
* Serving
  - serving.knative.dev/v1 (knative-serving v1.13.0)
* Eventing
  - sources.knative.dev/v1 (knative-eventing v1.13.0)
  - eventing.knative.dev/v1 (knative-eventing v1.13.0)
➜  kn-hello-func git:(main) ✗ kn func version
v0.39.0-1-g4b6247d0

func.yaml

specVersion: 0.35.0
name: kn-hello-func
runtime: go
registry: docker.io/ivishalyadav
created: 2024-02-08T11:43:05.053846598+05:30

Logs

➜  kn-hello-func git:(main) ✗ kn func run --build --registry docker.io/ivishalyadav --verbose
Building function image
Pulling image ghcr.io/knative/builder-jammy-tiny:latest
latest: Pulling from knative/builder-jammy-tiny
Digest: sha256:21d4966de6cda91bda7bfcf691ec69f13c3f1ae1bf405e907d042a828bad7228
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:2381406c9e5eebed510ab30350ecd2ef1ec43c38972e091a1493cb114ae9c5f7
Status: Image is up to date for paketobuildpacks/run-jammy-tiny:latest
Creating builder with the following buildpacks:
-> paketo-community/rust@0.35.0
-> paketo-buildpacks/procfile@5.6.4
-> paketo-buildpacks/syft@1.32.1
-> paketo-community/cargo@0.10.1
-> paketo-community/rust-dist@1.19.0
-> paketo-community/rustup@1.9.1
-> dev.knative-extensions.go@0.0.6
-> paketo-buildpacks/go@4.7.0
-> paketo-buildpacks/ca-certificates@3.6.7
-> paketo-buildpacks/environment-variables@4.5.6
-> paketo-buildpacks/git@1.0.8
-> paketo-buildpacks/go-build@2.2.0
-> paketo-buildpacks/go-dist@2.4.5
-> paketo-buildpacks/go-mod-vendor@1.0.28
-> paketo-buildpacks/image-labels@4.5.5
-> paketo-buildpacks/procfile@5.6.8
-> paketo-buildpacks/watchexec@2.8.7
-> paketo-buildpacks/java-native-image@8.26.0
-> paketo-buildpacks/bellsoft-liberica@10.4.5
-> paketo-buildpacks/ca-certificates@3.6.7
-> paketo-buildpacks/datadog@4.8.0
-> paketo-buildpacks/environment-variables@4.5.6
-> paketo-buildpacks/executable-jar@6.8.3
-> paketo-buildpacks/gradle@7.7.1
-> paketo-buildpacks/image-labels@4.5.5
-> paketo-buildpacks/leiningen@4.6.9
-> paketo-buildpacks/maven@6.15.12
-> paketo-buildpacks/native-image@5.12.7
-> paketo-buildpacks/procfile@5.6.8
-> paketo-buildpacks/quarkus@0.2.4
-> paketo-buildpacks/sbt@6.12.11
-> paketo-buildpacks/spring-boot@5.27.8
-> paketo-buildpacks/syft@1.42.0
-> paketo-buildpacks/upx@3.4.7
-> paketo-buildpacks/java@11.0.0
-> paketo-buildpacks/apache-tomcat@7.14.3
-> paketo-buildpacks/apache-tomee@1.8.0
-> paketo-buildpacks/azure-application-insights@5.17.3
-> paketo-buildpacks/bellsoft-liberica@10.5.2
-> paketo-buildpacks/ca-certificates@3.6.7
-> paketo-buildpacks/clojure-tools@2.8.14
-> paketo-buildpacks/datadog@5.1.0
-> paketo-buildpacks/dist-zip@5.6.8
-> paketo-buildpacks/encrypt-at-rest@4.5.13
-> paketo-buildpacks/environment-variables@4.5.6
-> paketo-buildpacks/executable-jar@6.8.3
-> paketo-buildpacks/google-stackdriver@8.0.4
-> paketo-buildpacks/gradle@7.7.1
-> paketo-buildpacks/image-labels@4.5.5
-> paketo-buildpacks/jattach@1.5.0
-> paketo-buildpacks/java-memory-assistant@1.4.9
-> paketo-buildpacks/leiningen@4.6.9
-> paketo-buildpacks/liberty@4.0.0
-> paketo-buildpacks/maven@6.15.12
-> paketo-buildpacks/node-engine@3.2.0
-> paketo-buildpacks/procfile@5.6.8
-> paketo-buildpacks/quarkus@0.2.4
-> paketo-buildpacks/sbt@6.12.11
-> paketo-buildpacks/spring-boot@5.27.8
-> paketo-buildpacks/syft@1.42.0
-> paketo-buildpacks/watchexec@2.8.7
-> paketo-buildpacks/yarn@1.3.0
-> paketo-buildpacks/procfile@5.6.8
Using build cache volume pack-cache-ivishalyadav_kn-hello-func_latest-f2dfafb0a74c.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/ivishalyadav/kn-hello-func:latest
  System Envs: CNB_PLATFORM_API=0.12
  Image: pack.local/builder/68637771726376636c79:latest
  User: root
  Labels: map[author:pack]
Host Settings:
  Binds: pack-cache-ivishalyadav_kn-hello-func_latest-f2dfafb0a74c.build:/cache /var/run/docker.sock:/var/run/docker.sock pack-cache-ivishalyadav_kn-hello-func_latest-f2dfafb0a74c.launch:/launch-cache pack-layers-ufrumcxuxo:/layers pack-app-ojbqdmsbyc:/workspace    
  Network Mode: host
Starting creator...
Parsing inputs...
Ensuring privileges...
Executing command...
===> ANALYZING
Timer: Analyzer started at 2024-02-09T07:22:16Z
Found image with identifier "454e51cec4a97ed3b7afb80ad108a0f96790f0da38d23d6885702e491e5b3902"
Found image with identifier "36643d2c344602e38bc4dc2aa0b06d98cf1a5509abc828c7e41eb6ca1dc8526a"
Timer: Analyzer ran for 70.425µs and ended at 2024-02-09T07:22:16Z
Run image info in analyzed metadata is:
{"Reference":"36643d2c344602e38bc4dc2aa0b06d98cf1a5509abc828c7e41eb6ca1dc8526a","Image":"index.docker.io/paketobuildpacks/run-jammy-tiny:latest","Extend":false,"target":{"os":"linux","arch":"amd64"}}
===> DETECTING
Timer: Detector started at 2024-02-09T07:22:16Z
Checking for match against descriptor: {linux amd64  [{ubuntu 18.04}]}
======== Output: paketo-buildpacks/procfile@5.6.4 ========
SKIPPED: No procfile found from either source path or binding.
======== Results ========
pass: paketo-community/rustup@1.9.1
pass: paketo-community/rust-dist@1.19.0
pass: paketo-buildpacks/syft@1.32.1
fail: paketo-community/cargo@0.10.1
skip: paketo-buildpacks/procfile@5.6.4
======== Results ========
pass: paketo-buildpacks/go-dist@2.4.5
pass: dev.knative-extensions.go@0.0.6
Resolving plan... (try #1)
paketo-buildpacks/go-dist 2.4.5
dev.knative-extensions.go 0.0.6
Timer: Detector ran for 34.128778ms and ended at 2024-02-09T07:22:16Z
===> RESTORING
Timer: Restorer started at 2024-02-09T07:22:16Z
Restoring Layer Metadata
Reading buildpack directory: /layers/paketo-buildpacks_go-dist
Reading buildpack directory: /layers/dev.knative-extensions.go
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/paketo-buildpacks_go-dist
Reading Buildpack Layers directory /layers
Reading buildpack directory: /layers/dev.knative-extensions.go
Timer: Restorer ran for 206.009µs and ended at 2024-02-09T07:22:16Z
===> BUILDING
Timer: Builder started at 2024-02-09T07:22:16Z
Running build for buildpack paketo-buildpacks/go-dist@2.4.5
Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command
Paketo Buildpack for Go Distribution 2.4.5
  Resolving Go version
    Candidate version sources (in priority order):
      <unknown> -> ""

    Selected Go version (using <unknown>): 1.20.14

  Executing build process
    Installing Go 1.20.14
      Completed in 20.297s

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

Processing layers
Updating environment
Reading output files
Updating buildpack processes
Updating process list
Finished running build for buildpack paketo-buildpacks/go-dist@2.4.5
Running build for buildpack dev.knative-extensions.go@0.0.6
Looking up buildpack
Finding plan
Creating plan directory
Preparing paths
Running build command
> Knative Functions Go Buildpack
  Fetching framework dependencies
go: malformed module path "function/faas": missing dot in first path element
Timer: Builder ran for 20.357803646s and ended at 2024-02-09T07:22:37Z
ERROR: failed to build: exit status 1
Error: executing lifecycle: failed with status code: 51
Error: exit status 1

[Sanket-0510]

@lkingland Can i look into this?

[Vishal1297]

I forgot to mention that this is happening in WSL.

[lkingland]

@lkingland Can i look into this?

Yes, please. I see Matej already set you as assignee 👍

[Sanket-0510]

1. After digging into this, I discovered that functions were initially referred to as "faas" in the Knative Func repository. However, everything was later renamed to "function" after pull request feat!: rename faas to function #210.

2. According to the error, the build process is attempting to execute code that requires a module named "function/faas". However, this path is missing a domain name and appears to be a source directory.

I'm not sure if there's any connection between these two points, but I couldn't find any explicit mention of the "function/faas" module in the Func repository.

Can someone elaborate over this?

[matejvasek]

@Sanket-0510 can you at least reproduce this issue? I do not recall running into this on Linux.

[Sanket-0510]

@matejvasek I am on linux, I tried reproducing this error but on my side the function was build successfully, no such error. @Vishal1297 can you verify this again, are you still facing this issue?

[Vishal1297]

@matejvasek I am on linux, I tried reproducing this error but on my side the function was build successfully, no such error. @Vishal1297 can you verify this again, are you still facing this issue?

I faced this issue only once and I got error after doing a change in go module name (github.com/Vishal1297/function)

[Vishal1297]

Hello, I am able to reproduce this issue.

Steps To Reproduce [OS: Linux]

• func create -l go kn-hello-func
• Delete go.mod file
• go mod init github.com/username/kn-hello-func (remote repo doesn't exists)
• func build