Jonas Schneider

I think it's because we use the github.com/golang/protobuf/protoc-gen-go tool in tools.go. In grpc [quickstart](https://grpc.io/docs/languages/go/quickstart/) it looks like the new package has a similar compiler

```sh $ go mod why -m github.com/golang/protobuf # github.com/golang/protobuf agones.dev/agones/pkg/allocation/go github.com/golang/protobuf/descriptor ``` So it seems like no other dependency is used, but the api chaned quite a bit (e.g. ptypes...

I have the same issue (two collisions) but with all patches that are under third-party none fix the issue for me and I don't know which dependency i misdeclared or...

> You should checkout [this documentation](https://github.com/bazelbuild/rules_go/blob/master/go/dependencies.rst#go_rules_dependencies). Can you give any advice for what you meant by that :D

i've implemented this today and will be pushing a pr soon: - These two ruleConverters create the two options https://github.com/typescript-eslint/tslint-to-eslint-config/blob/470d44de20beb7c7366de993edb8898d0766b8aa/src/converters/lintConfigs/rules/ruleConverters/jsx-curly-spacing.ts#L7-L14 https://github.com/typescript-eslint/tslint-to-eslint-config/blob/470d44de20beb7c7366de993edb8898d0766b8aa/src/converters/lintConfigs/rules/ruleConverters/react-tsx-curly-spacing.ts#L7-L14 the only thing is: i don't know what to...

I did some further digging: Via /service/token?account=[username]&offline_token=true&service=harbor-registry&client_id=docker i can get a token. When queriying /v2/ With the given Authorization: Bearer [token] Header and the csrf token. A 400 Bad Request...

> Same error here. I'm my case I'm able to run helm repository login without any issue, but docker login throws error 400... I never tested it until now. But...

Unfortunately I am stuck with traefik. But it shouldn't matter since all Authorization headers get forwarded successfully (since it would say 401 otherwise i think). In version v1.13.2 the issue...

unfortunately even with a nginx intermediate proxy like @TheMatrix97 it is not working. As well as when i use nginx as deployed in cluster ip expose mode and just port-forward...

I just updated to 1.14.1 helm chart and Harbor 2.10 and the problem still persists