-
Notifications
You must be signed in to change notification settings - Fork 242
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
constants.go #12
Comments
Can you provide the outputs of: I just built the latest go release in a vagrant box from scratch. The package builds and tests without issue.
If you'd like I can provide the vagrant configuration so you can verify. In the future, please open issues in the repository the problem relates to rather than repositories where the issue is in a dependency. Or if a previous issue, comment there. |
Hi, here's the output
Good point, I should have put the issue in the other repository. Also, I put the two returns into the code last night and everything is working fine after that change and tuning the frequency to match my meter. |
The go version string looks like you aren't running the latest release. If you built go from scratch but didn't add the new go binary to the path then you may still be executing the old version. What do |
That could be the issue, I'll poke around to see where it was built. In the mean time the path info --
|
Yeah, that confirms it, you may have built the latest release from source but the previous version is what is being executed. You'll want to remove the old version. |
The code will stay as it is because I've only tested with Go 1.2 and up. The errors serve as a sort of canary for issues submitted as a result of using an unsupported version. |
Hi, I have the same issue that was reported prior ---
I installed the latest go from source and tried to no avail. Can you drop a few extra returns in the .go file? I hate to fork the entire project for something silly like a missing return, or maybe that's the right thing (hey, I'm new here).
Many thanks.
The text was updated successfully, but these errors were encountered: