-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
v1.4 dies with "runtime error: integer divide by zero" on linux #18
Comments
@leberknecht Thank you for the report! Curious, within the same session in which you've launched Popeye, can you double check using kubectl get svc
popeye and report what this yields? I am thinking something isn't quiet right with your kubeconfig context and hence causing Popeye to fail?? |
Sure :)
as said, works fine with v.0.1.3 |
@leberknecht Thank you for reporting back! This is strange. I noticed your cluster does not have a name so I think there is problem with popeye connecting to the api server. I think my connectivity check is a dud so I'll fix that. In the mean time, to make sure this is not a release issue. Would you mind trying the tarball directly from the release1.4 page and see if it goes any further? Thank you!! |
Hm! The version from the release page does indeed work! delf % md5sum /snap/bin/popeye #broken
84aa51611afbf02bba0516d9f1e9fd8d /snap/bin/popeye
delf % md5sum Downloads/popeye #works
b3e0dc5390c14953d49a2bcbd1503292 Downloads/popeye Solves my problem :) Thank you! |
@leberknecht Thank you so much for looking into it and for your help on this!! Looks like something went south with that particular release on snap. Back to the drawing board ;( |
@leberknecht Can you given 0.2.0 a "snap" and see if we're happier in snap land? Thank you! |
Describe the bug
When running popeye, the "Connectivity" and "Metrics" steps seem to be ok (have a checkmark), but then i get (removed some newlines)
To Reproduce
Steps to reproduce the behavior:
popeye
Expected behavior
Should run through :) Im also surprised about the
with 0.1.3 everything works fine, so i doubt that it is a permissions issue.
Screenshots
Versions (please complete the following information):
Additional context
Also wondering (not that familiar with golang): is it normal to have the path
/Users/fernand
in the exception message? User doesnt exist here, but i guess this is some kind of go-package-effect?The text was updated successfully, but these errors were encountered: