Alexandr Burdiyan

@ivanjaros This wrapper seems to provide indexing functionality. Badger itself knows nothing about indexing. So I assume this is the correct suggestion here.

@ivanjaros There's probably a misunderstanding somewhere, maybe in what we all refer to as indexes. For context, I'm well aware of what Badger is, how LSM trees work and etc....

Just ran into this, and was also confused. What is the expected behavior here?

Same thing happening to me. `go version go1.8.3 darwin/amd64`.

Seems like it is related to this: https://github.com/gravitational/teleconsole/issues/16 Looks like Teleconsole was using old version of Teleport, that is not vendored in Teleconsole. But I still can't manage to build...

Just got hit by this. Renovate just updated Go version in the go.mod files in our manually vendored third-party dependencies and merged everything. We also are using Nix + nix-shell...

I'd like to give it a try, but first would like to have it super clear in terms of the design. >So goka.Context is an interface anyway. Whenever writing some...

Just read the thread and from the high level it seems pretty reasonable, although conceptually there’s something I don’t like about the idea of duplicating core functions (goka.Stream and etc.)...

i could see it being something along these lines (from a very hight level perspective): 1. We could have a new `goka.Edge` that would create a group table. Same thing...

@db7 In Kafka Streams, time is advanced only when new messages are coming. So basically it could be something like this when we process a new message: ``` if windowExist(message):...