Trouble Shooting¶

Go: log.Fatalf is Bad for Framework Maintainers

In the open source framework, as long as maintainers can ensure the issues are caused by users instead of the framework, usually they could provide some suggestive guides and prevent themselves from delving into users code.

However, as a company scope framework maintainer, things differ greatly. As you claimed your framework helps them to write better code based on the company platforms, they're likely to rely on the maintainers to figure out some weird issues once it's related with the framework.

This blog records how I help to trouble shoot the weird issue of keeping restarting and failed to deploying caused by the log.Fatalf for our framework users, and my opinion why the log.Fatalf is bad.

Migration from Docker to OrbStack

Recently, my company abandoned docker desktop because it requires the company to paid for its services. As a result, the company treats as an unnecessary cost and asks the developers to find another alternatives. This blog records the troublesome during my migration.

Company IPS Plays MITM for the openai.com

Recently, one of my friends told my company alerts you when you open the openai to suggest you use the company's internal gpt tool. However, the browser still treats this connection as secure because it satisfies the HTTPs requirement.

This is indeed the man-in-the-middle attack, which hijacks your connections as the middle man and then establish another connection to communicate. The root cause is that in your company device, the certificates of company's ISP are forcibly trusted. As a result, technically they could monitor and modify your requests when necessary.

Go Cgo: stdlib.h Not Found after Upgrading

After upgrading macOs, my go breaks as it cannot find the stdlib.h:

BUILD| runtime/cgo
     | _cgo_export.c:3:10: fatal error: 'stdlib.h' file not found

Memory Consuming Issue of Logging Lib

One of users reported he found the RPC logging interceptor consumes a lot of memory, so we checked the profiler first and then found the image below and the blabla is the underlying log library.

This blog records how to do troubleshooting this issue. However, as lacking more details, I handed over the issue to the log team for further checking.