zerolog | overhead logging façade

Thanks to the help I got it working:

I changed the datatype of taxper to float and it worked. I found this after checking the err from rows.Scan( as suggested by @mkopriva

Use an empty handler (a handler function whose body is empty: {}). If you write nothing to the response writer and set no status code, HTTP 200 OK will be sent back by default.

You may also use an anonymous function (function literal):

After some experiments, I can confirm my issue is not related with Linkerd.

I think my PostgreSQL containerPort/targetPort is still using the default 5432. And it exposed by ClusterIP inside of the network by port 40072, which is why I don't need mark the port as opaque in Linkerd.

It turns out that after adding os.Exit(1),

The Transport.RoundTrip function takes a *http.Request parameter, so you should be able to pass the Gin context by just creating a request in your handlers with it:

Declare Logger in a different package called logger or something and use logger referring it in all packages

Set a unique id on a context.Context as soon as the request is received, and pass that context down the call stack. This is what contexts are for.

[Context] carries deadlines, cancellation signals, and other request-scoped values across API boundaries and between processes.

Example:

Static initializer for Logging.fs file is not being called (12.5.1 Execution of Static Initializers) because it's not an entry point file and you are not accessing any value which has observable initialization (yes, that's a vague definition). The point is - if static initializer wasn't called, then logManager value wasn't initialized. Which means in your case that all logger configuration code wasn't executed.

The simplest way to make sure logger is initialized is to move initialization logic to function and call it explicitely:

the reason is that you are not escaping your regular expression of query string. Sqlmock expects regular expression in your expectation.

Now in case if you want to match exact query string, not parts of it. You can specify an sqlmock mock option, like this: