Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

window10,go v1.23.4 generate-groups.sh all: error: #180

Open
hzrunit opened this issue Dec 18, 2024 · 1 comment
Open

window10,go v1.23.4 generate-groups.sh all: error: #180

hzrunit opened this issue Dec 18, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@hzrunit
Copy link

hzrunit commented Dec 18, 2024

paltform:windows10,go v1.23.4,git
projetct structure:
/d/test_go_learn/
├── code-generator/
│ ├── generate-groups.sh
│ ├── hack/
│ │ └── boilerplate.go.txt
│ └── vendor/
├── operator-crd/
│ ├── pkg/
│ │ ├── generated/
│ │ └── apis/
│ └── go.mod

on the git bash to exec:
$ ./generate-groups.sh all github.com/operator-crd/pkg/generated github.com/operator-crd/pkg/apis crd.example.com:v1 --go-header-file=./hack/boilerplate.go.txt
Generating deepcopy funcs
Generating clientset for crd.example.com:v1 at github.com/operator-crd/pkg/generated/clientset
F1218 17:09:20.401085 52588 main.go:62] Error: Failed executing generator: some packages had errors:
errors in package "github.com\operator-crd\pkg\generated\clientset\versioned":
unable to format file "D:\workspace\go_learn\src\github.com\operator-crd\pkg\generated\clientset\versioned\clientset.go" (23:20: unknown escape sequence (and 4 more errors)).

errors in package "github.com\operator-crd\pkg\generated\clientset\versioned\fake":
unable to format file "D:\workspace\go_learn\src\github.com\operator-crd\pkg\generated\clientset\versioned\fake\clientset_generated.go" (23:24: unknown escape sequence (and 13 more errors)).

goroutine 1 [running]:
k8s.io/klog/v2.stacks(0x1)
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:1038 +0x85
k8s.io/klog/v2.(*loggingT).output(0x12d9520, 0x3, 0x0, 0xc000090e00, 0x0, {0x110561a?, 0x1?}, 0xc000096f80?, 0x0)
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:987 +0x60f
k8s.io/klog/v2.(*loggingT).printf(0x12d9520, 0x3, 0x0, {0x0, 0x0}, {0xfbcfa8, 0x9}, {0xc000096f80, 0x1, 0x1})
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:753 +0x1c7
k8s.io/klog/v2.Fatalf(...)
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:1532
main.main()
D:/test_go_learn/code-generator/cmd/client-gen/main.go:62 +0x345

goroutine 6 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0x12d9520)
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:1181 +0x66
created by k8s.io/klog/v2.init.0 in goroutine 1
D:/workspace/go_learn/pkg/mod/k8s.io/klog/[email protected]/klog.go:420 +0xcf

XXXX@CLM-0073 MINGW64 /d/test_go_learn/code-generator ((kubernetes-1.23.5))
$ sh -x ./generate-groups.sh all github.com/operator-crd/pkg/generated github.com/operator-crd/pkg/apis crd.example.com:v1 --go-header-file=./hack/boilerplate.go.txt

  • set -o errexit
  • set -o nounset
  • set -o pipefail
  • '[' 5 -lt 4 ']'
  • '[' all == --help ']'
  • GENS=all
  • OUTPUT_PKG=github.com/operator-crd/pkg/generated
  • APIS_PKG=github.com/operator-crd/pkg/apis
  • GROUPS_WITH_VERSIONS=crd.example.com:v1
  • shift 4
    ++ dirname ./generate-groups.sh
  • cd .
  • GO111MODULE=on
  • go install k8s.io/code-generator/cmd/defaulter-gen k8s.io/code-generator/cmd/client-gen k8s.io/code-generator/cmd/lister-gen k8s.io/code-generator/cmd/informer-gen k8s.io/code-generator/cmd/deepcopy-gen
    ++ go env GOBIN
  • GOBIN=
    ++ go env GOPATH
  • gobin='D:\workspace\go_learn\bin'
    ./generate-groups.sh: line 59: `codegen::join': not a valid identifier
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants