When running as a gin subprocess, the stdout pipe for the underlying server process is no longer connected to a TTY. This can affect things such as formatting choices made by logging frameworks like logrus.
I'm guessing that the reason for this is that gin is creating a pipe and manually copying things over to the "outer" output stream. If gin instead explicitly transferred ownership of its own stdout and stderr pipes to the subprocess then the subprocess would see them as TTYs.
When running as a gin subprocess, the stdout pipe for the underlying server process is no longer connected to a TTY. This can affect things such as formatting choices made by logging frameworks like logrus.
I'm guessing that the reason for this is that gin is creating a pipe and manually copying things over to the "outer" output stream. If gin instead explicitly transferred ownership of its own stdout and stderr pipes to the subprocess then the subprocess would see them as TTYs.