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

Error stack trace still shows the user GOPATH #1530

Closed
BuddhiWathsala opened this issue Jun 7, 2019 · 4 comments · Fixed by #1535
Closed

Error stack trace still shows the user GOPATH #1530

BuddhiWathsala opened this issue Jun 7, 2019 · 4 comments · Fixed by #1535
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@BuddhiWathsala
Copy link

Bug Report

What did you do?
Panic

What did you expect to see?
A stack trace without any GOPATH.

What did you see instead? Under which circumstances?
Some of the paths still show my entire GOPATH.

{"level":"error","ts":1559906945.9563708,"logger":"controller_siddhiprocess","msg":"CRD should only contain either query or app entry","Request.Namespace":"default","Request.Name":"nats-app","error":"CRD should only contain either query or app entry","stacktrace":"github.com/siddhi-io/siddhi-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/github.com/go-logr/zapr/zapr.go:128
github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess.(*ReconcileSiddhiProcess).Reconcile
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/pkg/controller/siddhiprocess/siddhiprocess_controller.go:171
github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215
github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until
	/Users/buddhi/Documents/MyWork/Go/src/github.com/siddhi-io/siddhi-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

Environment

  • operator-sdk version v0.5.0+git
  • go version:

go version go1.12 darwin/amd64

  • Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"
go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:28:14Z", GoVersion:"
go1.11.4", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes cluster kind: minikube version: v0.33.1

  • Are you writing your operator in ansible, helm, or go? Go

Additional context
I refer to the following issues.
[1]: #1036
[2]: golang/go#13809 (reference)

But I cannot understand why I'm still getting this GOPATH in my error stack trace.

@lilic
Copy link
Member

lilic commented Jun 7, 2019

cc @AlexNPavel you worked on #1036 you might have an idea on this.

@joelanford joelanford added the kind/bug Categorizes issue or PR as related to a bug. label Jun 7, 2019
@BuddhiWathsala
Copy link
Author

I also tried the operator-sdk version: v0.8.1 but getting the same issue.

@AlexNPavel
Copy link
Contributor

We found the issue and will be making a PR to fix it shortly

@BuddhiWathsala
Copy link
Author

Now it solved. I compile operator-sdk from source and install from the master branch. Hope you will release this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants