Jelle Vink

@rriolobos I have updated your sample code a bit to try to reproduce and created two samples: - [Without ordering](https://gist.github.com/skymeyer/14d6e45321574241d50647b2f03fb3b4#file-pubsub-no-order-main-go) --> [output](https://gist.github.com/skymeyer/14d6e45321574241d50647b2f03fb3b4#file-pubsub-no-order-output-txt) - [With ordering](https://gist.github.com/skymeyer/14d6e45321574241d50647b2f03fb3b4#file-pubsub-with-order-main-go) --> [output](https://gist.github.com/skymeyer/14d6e45321574241d50647b2f03fb3b4#file-pubsub-with-order-output-txt) Ordering seems to...

@fgimenez I ran into the same issue recently. Can you check if you have a `go_repository` entry somewhere referencing `com_github_bazelbuild_buildtools` ? I had to pin it to the exact same...

Reproducible for both situations using `sail run` and the error message when trying with the extension. ``` OSX 10.14.6 Chrome 80.0 Docker Desktop 2.2.0.4 Docker 19.03.8 ```

This definitely would be great to have +1

Just tested gitlab and that seems to work as well for me. The only spec I know of is what is described in https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols. If a git server implements both...

I'd defer that to later yes if we have concrete short comings, I think we are good like it is for now.

I'll take a look over the weekend what we are missing. Regardless of that, I have some newer code sitting ready so we can abandon the legacy format all together...

I have been pretty busy the last months and completely overlooked finishing this up. The new code solely makes use of the JSON data simplifying the whole code base.

Thanks for your contribution, I'll get this reviewed and tested the next days. #32