go-micro | A Go microservices framework | Microservice library

It turns out Godog doesn't trim the Steps from the feature files.

So, In my feature files, the steps for the above lines included:

When reading resource of id "ID1"_____(blank space)

The regex pattern therefore wasn't able to map the step definitions to these lines for some reason.

As soon as I removed the empty spaces, it worked great.

The box-sizing CSS property sets how the total width and height of an element is calculated.

Try setting all elements box-sizing default to border-box like this:

Its a bug with version inconsistency between go-micro and grpc. About a week ago I tried to follow the tutorial which you mention and got same error. If you want to fix the error above please follow the interactions below the link: https://github.com/etcd-io/etcd/issues/11563.

In additionally I recommend you just build grpc service without go-micro, due to version inconsistency.

&mut always acquires a (compile time or runtime) exclusive lock to the value. Only acquire a &mut at the exact scope you want to get locked. If a value owned by the locked value needs separate locking management, wrap it in a Mutex.

Assuming your DbConnectionPool is structured like this:

You must have protoc and the plugin (protoc-gen-micro) installed.

I think you omitted the second step.

See:

https://github.com/micro/protoc-gen-micro

And perhaps:

A couple more days at this and I eventually worked out the issues myself, and learned a little more about how Django works too.

The link I was missing was how/where context processors from (third party) Django modules pass their context's through to the page that's eventually rendered. I didn't realise that variables from the microsoft_auth package (such as the authorisation_url used in its template) were accessible to me in any of my templates by default as well. Knowing this, I was able to implement a slightly simpler version of the same JS based login process that the admin panel uses.

Assuming that anyone reading this in the future is going through the same (learning) process I have (with this package in particular), I might be able to guess at the next couple of questions you'll have...

The first one was "I've logged in successfully...how do I do anything on behalf of the user?!". One would assume you'd be given the user's access token to use for future requests, but at the time of writing this package didn't seem to do it in any obvious way by default. The docs for the package only get you as far as logging into the admin panel.

The (in my opinion, not so obvious answer) is that you have to set MICROSOFT_AUTH_AUTHENTICATE_HOOK to a function that can be called on a successful authentication. It will be passed the logged in user (model) and their token JSON object for you to do with as you wish. After some deliberation, I opted to extend my user model using AbstractUser and just keep each user's token with their other data.

models.py