serverbuild | An easy-to-use Discord server cloner | Bot library

The InProcess transport is what you want. It is a full-fledged transport, but uses method calls and some tricks to avoid message serialization. It is ideally suited to testing, but is also production-worthy. When used with directExecutor(), tests can be deterministic. InProcess transport is used in the examples. See HelloWorldServerTest for one usage.

You can simply declare a volume in docker-compose.yml inside the service, a concept you are using already. Simply do ./app:/var/www/app/

I would also like to advise you to use COPY instead of ADD when copying files.

I don't know what you mean with For development is it possible to ALIAS instead of ADD ? so I can't help you there unless you clarify that point but this should make what you want.

Change your compile command to

I believe it is not possible, because each service is added to a map,

It seems to be a problem of the grpc package.

2nd part of the accepted answer of Linking gRPC on Windows for VisualC++ exactly fixed my problem.

I added #pragma comment(lib, "Ws2_32.lib") to my cpp-file and the problem was gone.

It also can be fixed like so (I've taken the screenshot from Unresolved external symbol LNK2019):

You are using the -trimpath option when building the plugin but not when building the app. Edit the docker file so both builds use -trimpath (or neither do) then the application will run (well it does on my machine).

My guess as to why this causes the issue is that trimpath "removes all file system paths from the compiled executable" so when the runtime verifies versions it picks up the difference in the paths.

Here is the dockerfile that works for me (having replicated the issue with the original; the only change is adding -trimpath to the second go build):

Hello from the gRPC team! The code looks fine to me. From the error message, it seems the server is not able to receive the client's certificates, while you apparently already set them in your client code. Could it be possible that your client certificates have some format issues, that are not recognized by the client stack?

To make sure it's not the problem with the client's cert, you can simply replace the client certs with server's certs(as well as the private key), and see if it works, since they are both signed by the same CA.

If the problem still persists, then we at least know the client's certs are good. I will probably reproduce on my end and see if I could see the same error.

The libzmq crate is just a wrapper for the libzmq C library. In the documentation for the C library, you will find this note:

NOTE: A successful invocation of zmq_msg_send() does not indicate that the message has been transmitted to the network, only that it has been queued on the 'socket' and 0MQ has assumed responsibility for the message.

In your first example, since the program exits immediately after calling send, the message is still in the libzmq queue and has not been transmitted yet. In your second example, the message gets transmitted while your program is waiting in the recv call.