Sebastian Rühl
Sebastian Rühl
In plc4go we pass them down the chain either use arguments or the ctx. Default handler works too but keep in mind then it is impossible to define different loggers...
Oh and to give you (@magiconair) a usecase which is quite vital at the moment: I have a application which produces humongous amount of logs. In that application opcua is...
good question: I haven't looked into slog too much as we use zerolog all over the place but from the looks of it Handler might be the better way.
AFAIK a handler would then look like this: ```golang type ZerologHandler struct { logger zerolog.Logger } func (h *ZerologHandler) Log(level slog.Level, msg string, kvs ...interface{}) error { var zerologLevel zerolog.Level...
yeah we use matrix because we need to build for different architectures...
@chenrui333 any idea how to mitigate. Maybe with a retry?
code point for reference https://github.com/incu6us/goimports-reviser/blob/5f29621b9217398814dbf41a021f51536cb54be1/reviser/dir.go#L138
~would be good to at least output the path in the error message to, otherwise the error looks a bit silly as can be seen above~ (edit: fixed with #163...
ok guess the title is wrong, it actually crashes because of the idea template (with the help of #163): `.idea/fileTemplates/includes/File Header Go.go`. So I was able to fix this by...
just ran into the same issue where the server json is just broken and I need to "enforce" xml. Poking around but I might up manipulating the swagger to to...