-
Notifications
You must be signed in to change notification settings - Fork 350
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 when building from source #421
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: docs
Improvement to the documentation for an API.
Comments
roger2hk
added
the
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
label
Jul 27, 2020
shubha-rajan
added
the
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
label
Jul 27, 2020
Do you know which version of Go you are using? I was able to replicate successfully with We may need to update the README to include explicit instructions for each version... |
Here is the output of
|
You are right. It works by adding the
|
kurtisvg
added
type: docs
Improvement to the documentation for an API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
and removed
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Jul 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: docs
Improvement to the documentation for an API.
Bug Description
There is an error when building from source.
Not sure why it happens as PR #382 pinned the
bazil.org/fuse
version.Example code (or command)
Stacktrace
How to reproduce
go get
command mentioned in README.Environment
./cloud_sql_proxy -version
): N/AThe text was updated successfully, but these errors were encountered: