Use latest-drivers bblfsh image

[carlosms]

With the current bblfsh v2.90 a bblfshctl driver install fails for already installed drivers (context here).

This means we can get errors like this:

$ srcd parse uast ~/repos/gitbase-web/cmd/gitbase-web/main.go 
FATA[0000] could not stream: rpc error: code = AlreadyExists desc = driver already installed: go (image reference: docker://bblfsh/go-driver:latest): %s 

We should add the new --force flag to bblfshctl (which actually means ignore, not force), or use the new latest-drivers images.

[smacker]

The error mentioned in the issue is fixed here: src-d/sourced-ce#84
But we still can consider using latest-drivers image.

[smacker]

I have noticed one problem with latest-drivers. This image follows bblfshd release cycle. So it doesn't get updates when bugs are fixed in drivers or even new features are added.

As an example right now the latest drivers image is v2.9.1-drivers https://hub.docker.com/r/bblfsh/bblfshd/tags/ released 15 days ago.
But the java-driver is released 20 hours ago https://hub.docker.com/r/bblfsh/java-driver/tags/
It is 2 releases newer with changes:

• Fix roles for primitive types
• Support error codes

[smacker]

Right now we have very good example of why it's problem:
We have bblfsh-web v0.8.0 but it can't work with current latest drivers image. Only with a normal one because it requires newer drivers.

[campoy]

We should still fix this, though.
Currently "sql web sql" takes minutes due to the lag of installing every single driver.
It should start in seconds.

[smacker]

In my opinion, we need to discuss it with LA team and agree on some kind of schedule for -drivers releases or something like that.

Current release was made 24 days ago, since then in java-driver, for example, was created 3 new releases:

• Enable language namespace in Semantic UAST
• Annotate default function modifier.
• Normalize and annotate Javadoc nodes properly.

We need to incorporate those improvements into engine somehow at some point.

cc @creachadair

[creachadair]

The above sounds sensible to me. At the very least, it seems like we should have some coordination around which semantic version ranges are compatible with each other. Tightly-coupled releases are hard to maintain, but there should be some middle ground between that and confusing/surprising behaviour for the user.

[smacker]

here is the change to -drivers image: src-d/sourced-ce#135

but it still downloads cpp driver separately. Because cpp driver is recommended already but isn't included in latest drivers image. (one more example why we need some kind of coordination with LA team)