-
Notifications
You must be signed in to change notification settings - Fork 349
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
Panic when fuse fails to start #2013
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
enocom
added
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
labels
Oct 31, 2023
enocom
added a commit
that referenced
this issue
Apr 25, 2024
If the fuse server fails to mount, the call to Close should not panic. This commit ensures that no panic's happen if fuse isn't properly configured. Fixes #2013
enocom
added a commit
to GoogleCloudPlatform/alloydb-auth-proxy
that referenced
this issue
Apr 25, 2024
If the FUSE mount has not succeeded due to misconfiguration, the Proxy should still shutdown without panicing. Related to GoogleCloudPlatform/cloud-sql-proxy#2013
This was referenced Apr 25, 2024
enocom
added a commit
to GoogleCloudPlatform/alloydb-auth-proxy
that referenced
this issue
Apr 25, 2024
If the FUSE mount has not succeeded due to misconfiguration, the Proxy should still shutdown without panicing. Related to GoogleCloudPlatform/cloud-sql-proxy#2013
enocom
added a commit
to GoogleCloudPlatform/alloydb-auth-proxy
that referenced
this issue
Apr 25, 2024
If the FUSE mount has not succeeded due to misconfiguration, the Proxy should still shutdown without panicing. Related to GoogleCloudPlatform/cloud-sql-proxy#2013
enocom
added a commit
that referenced
this issue
Apr 26, 2024
If the fuse server fails to mount, the call to Close should not panic. This commit ensures that no panic's happen if fuse isn't properly configured. Fixes #2013
enocom
added a commit
that referenced
this issue
Apr 26, 2024
If the fuse server fails to mount, the call to Close should not panic. This commit ensures that no panic's happen if fuse isn't properly configured. Fixes #2013
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: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
When the fuse binary is missing, the user doesn't have read access, user_allow_other isn't set, etc., the Proxy will panic instead of reporting the error and exiting gracefully.
Stacktrace:
The text was updated successfully, but these errors were encountered: