Maxim Sukharev
Maxim Sukharev
It makes sense to improve error message disregard of this issue
@carlosms We started a discussion in 2 different places: PR and slack. I think it's better to move it here. The discussions touch different topics, I'll try to summarize them...
I still think DB & Bblfsh are critical components for lookout and we should report non 200 status when they are not available. Plus the concern of a restart in...
I don't think you can [define](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#define-a-liveness-http-request) more than 1 endpoint for readness and liveness checks in kubernetes. So it should be the same endpoints.
I used as example this PR: https://github.com/bblfsh/uast-viewer/pull/89 it is created from a local branch `greenkeeper/react-styleguidist-9.0.0` In the `events` endpoint I see such events: - CreateEvent: ``` id "9101240193" type "CreateEvent"...
Actually we are using/going to use `esc` in different projects. And not only apps projects. Do you think it makes sense to include it into `ci` repo, similar to [dep](https://github.com/src-d/ci/blob/v1/Makefile.main#L245)?
if we are talking about ci I'm not sure fixed version should depend on package manager as go mod or dep. As an example, `godep` target depends on neither of...
also CI is failing
I really like `wget` solution. It is similar to `godep` one and simpler. And I think we can pull request it directly into `ci` repo. On another hand, I'm absolutetly...
ping @carlosms