Closed hkhk367 closed 2 years ago
Similarly, we've noticed problems running logrus in K8S/Docker environments, where the error is generated from logrus, not from the file/location where the error apparently occurred. I say, "similarly", since GoLand runs in a mock env.
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
I'm not sure if this is a logrus problem, but if not I'll report the bug on goland.
After clicking the run button on goland, there is a lot of blank space on the right side of the output window, whereas this problem does not occur with fmt.Println() or other libraries.
When I run with "go run .", logrus does not have this problem.
Is this a logrus problem or a goland problem? Thank you.
The following are parts of my codes.