-
Notifications
You must be signed in to change notification settings - Fork 1
Enabled monitors #14
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
Enabled monitors #14
Conversation
| func queryHandler(w http.ResponseWriter, r *http.Request) { | ||
| entryString := os.Getenv("MYSQL_USER")+":"+os.Getenv("MYSQL_USER_PASSWORD")+"@"+"tcp("+os.Getenv("MYSQL_HOST")+":3306)/"+os.Getenv("MYSQL_DB_NAME") | ||
| //entryString := os.Getenv("MYSQL_USER")+":"+os.Getenv("MYSQL_USER_PASSWORD")+"@"+"tcp("+os.Getenv("MYSQL_HOST")+":"+os.Getenv("MYSQL_PORT")+")/"+os.Getenv("MYSQL_DB_NAME") | ||
| entryString := "root:PASSWORD@tcp(dockerVM:3306)/stuff" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a test line
| return | ||
| default: | ||
| stat := (<-container.statsChannel) | ||
| if(stat == nil) {panic("Received Nil from container")} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this require a panic error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VincenzoFerme Because a nil means the socket isn't receiving anything, which seems to imply something has gone seriously wrong with the docker socket.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Cerfoglg Can this happen during the execution or only when the execution starts? I guess the first, right? If that is the case I would say we need a better way to handle this error, by reporting the status to the client.
fixes #11