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

bad error messages when ./vatz start #282

Closed
1 of 4 tasks
xellos00 opened this issue Oct 19, 2022 · 0 comments · Fixed by #289
Closed
1 of 4 tasks

bad error messages when ./vatz start #282

xellos00 opened this issue Oct 19, 2022 · 0 comments · Fixed by #289
Assignees
Labels
area:svc Anything related to Vatz Service. type:bug Bug report and fix Vatz Project Name

Comments

@xellos00
Copy link
Member

xellos00 commented Oct 19, 2022

Checklist

  • Bug from Service (Vatz)
  • Bug from Plugin (Vatz)
  • Malfunction on CI/CD
  • etc(e.g, Hardware version doesn't match, )

Describe the bug

A clear and concise description of what the bug is.

VATS start command returns panic if a default config file is not exist.
Issue were fixed #259 but been override through development on #277
There's Error Message that is not appropriate even if Vats started properly.

How to Reproduce

Steps to reproduce the behavior:

  1. Execute Command make build
  2. Execute Command ./vatz init
  3. Execute Command ./vatz start or ./vatz --config default2.yaml

image

 dongyookang DK 🚦   ~/ffplay/GolandProjects/xellos/vatz   main ±
 make build
fatal: No names found, cannot describe anything.
go build -ldflags="-X 'main.Version=main' -X 'main.Commit=d9c1036'" -v
 dongyookang DK 🚦   ~/ffplay/GolandProjects/xellos/vatz   main
 ./vatz init 
2022-10-18T19:51:37-05:00 INF init module=main
2022-10-18T19:51:37-05:00 INF create file default.yaml module=main
 dongyookang DK 🚦   ~/ffplay/GolandProjects/xellos/vatz   main
 ./vatz start
2022-10-18T19:51:48-05:00 INF start module=main
2022-10-18T19:51:48-05:00 INF load config default.yaml module=main
2022-10-18T19:51:48-05:00 INF logfile  module=main
2022-10-18T19:51:48-05:00 ERR Load Config default.yaml module=config
2022-10-18T19:51:48-05:00 INF Initialize Servers: VATZ Manager module=main
2022-10-18T19:51:48-05:00 INF VATZ Listening Port: :9090 module=main
2022-10-18T19:51:48-05:00 INF VATZ Manager Started module=main
2022-10-18T19:51:48-05:00 INF start rpc server module=rpc
2022-10-18T19:51:48-05:00 INF start gRPC gateway server 127.0.0.1:19091 module=rpc
2022-10-18T19:51:48-05:00 INF start gRPC server 127.0.0.1:19090 module=rpc

image

 ✘ dongyookang DK 🚦   ~/ffplay/GolandProjects/xellos/vatz   main
 ./vatz start --config default2.yaml
2022-10-18T19:53:27-05:00 INF start module=main
2022-10-18T19:53:27-05:00 INF load config default2.yaml module=main
2022-10-18T19:53:27-05:00 INF logfile  module=main
2022-10-18T19:53:27-05:00 ERR Load Config default2.yaml module=config
2022-10-18T19:53:27-05:00 INF Initialize Servers: VATZ Manager module=main
2022-10-18T19:53:27-05:00 INF VATZ Listening Port: :9090 module=main
2022-10-18T19:53:27-05:00 INF VATZ Manager Started module=main
2022-10-18T19:53:27-05:00 INF start rpc server module=rpc
2022-10-18T19:53:27-05:00 INF start gRPC gateway server 127.0.0.1:19091 module=rpc
2022-10-18T19:53:27-05:00 INF start gRPC server 127.0.0.1:19090 module=rpc

Expected behavior

A clear and concise description of what you expected to happen.

No Error message if ./vatz start properly

Screenshots

If applicable, add screenshots to help explain your problem.

@xellos00 xellos00 added Vatz Project Name type:bug Bug report and fix area:svc Anything related to Vatz Service. labels Oct 19, 2022
@xellos00 xellos00 changed the title Re: open default.yaml: no such file or directory bad error messages when ./vatz start Oct 19, 2022
@xellos00 xellos00 self-assigned this Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:svc Anything related to Vatz Service. type:bug Bug report and fix Vatz Project Name
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant