<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Logging on Suyog Garg</title>
    <link>https://suyoggarg.com/tags/logging/</link>
    <description>Recent content in Logging on Suyog Garg</description>
    <image>
      <title>Suyog Garg</title>
      <url>https://suyoggarg.com/</url>
      <link>https://suyoggarg.com/</link>
    </image>
    <generator>Hugo -- 0.128.0</generator>
    <language>en</language>
    <copyright>Suyog Garg</copyright>
    <lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://suyoggarg.com/tags/logging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Prettify git log</title>
      <link>https://suyoggarg.com/en/posts/2026-07-08-pretty-git-log/</link>
      <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://suyoggarg.com/en/posts/2026-07-08-pretty-git-log/</guid>
      <description>Disclaimer: Based on Google Gemini-Pro prompts!
Let’s face it—the default git log output is a massive wall of plain text that is painful to scan. When you are working with a team, tracking down who did what and when can feel like reading a raw terminal dump.
Today, we are going to fix that. We will transform your Git log into an interactive, beautifully structured, and color-coded masterpiece tailored specifically for your terminal workspace.</description>
    </item>
    <item>
      <title>Setting up custom loggers in Python</title>
      <link>https://suyoggarg.com/en/posts/2026-06-06-logging-issues/</link>
      <pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate>
      <guid>https://suyoggarg.com/en/posts/2026-06-06-logging-issues/</guid>
      <description>Disclaimer: Based on Google Gemini outputs!
When building complex, multi-module Python projects, especially in data science, deep learning, or physics, managing console output is a nightmare. You are often caught in a binary trap: either you turn debugging off and see nothing, or you turn it on and get drowned in a wall of INFO and DEBUG noise from third-party libraries and internal modules.
To make matters worse, many heavy frameworks (like PyTorch, Bilby, or Hugging Face) initialize their own logging configurations right at import time.</description>
    </item>
  </channel>
</rss>
