go-example | Pipeline example written in go for gaia | Continous Integration library

Figured it out, posting here if anyone else stumbles on this.

The answer is simple - you need to embed the go_library rule within the go_image rule. Here is my cmd/hello/BUILD.bazel where I also embed the go image in a docker container

That docs is wrong, as reported here: https://github.com/golang/protobuf/issues/1336:

The documentation on https://github.com/protocolbuffers/protobuf/blob/master/docs/field_presence.md#go-example is incorrect. Using "optional" in proto3 makes the field be generated just as it would in proto2.

That doc is wrong. There are no Has methods in the generated code. Test for presence by comparing fields to nil.

Rewriting those examples correctly:

Thanks for the help, now I understood why my "working example" works and how to "Fix" my current issue:

To fix it I have to pass an instance of the implementation of the interface as it's pointed out that enums can only access static methods or an instance of the object to access the method that way.

Final Code

URL you are constructing is not in right format, it should be in format for example

You can try getting the date in this way ->http://127.0.0.1:8000/blog/archive/2021-01-07 instead of this -> http://127.0.0.1:8000/blog/archive/2021/01/07. This will be a more easy way to handle things what you want

You may missed the % sign when calling url template tag here:

Year-{{ date|date:"Y" }}

I think it should be:

Year-{{ date|date:"Y" }}

query { user(firstname:"Pierre} { lastname}}

if above is your graphql query then it should be

query

{ user(firstname:"Pierre"){ lastname} }

Next read this parameter firstname in your code and fetch the document accordingly

Any ideas why these two error happen?

You're getting those errors because of the missing array operator. The operator $and requires an array, which should be represented as bson.A.

And how to fix it?

Please see the following pipeline:

From the release notes of Django RestFramework and DRF 3.9 announcement they mentioned that

Deprecate the Router.register base_name argument in favor of basename. #5990

Which means, the argument base_name is no longer available from DRF=3.11 onwards and use basename instead

So, Change your router config as,