<?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>Troubleshooting on Mengboy 技术笔记</title>
    <link>https://www.mfun.ink/tags/troubleshooting/</link>
    <description>Recent content in Troubleshooting on Mengboy 技术笔记</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>zh-cn</language>
    <lastBuildDate>Mon, 06 Apr 2026 01:17:34 +0000</lastBuildDate>
    <atom:link href="https://www.mfun.ink/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude Code &#43; GitHub Actions CI Self-Healing Pipeline: Error Attribution, Minimal Patches, and Human Approval Gates</title>
      <link>https://www.mfun.ink/english/post/claude-code-github-actions-ci-self-healing-pipeline/</link>
      <pubDate>Mon, 06 Apr 2026 01:17:34 +0000</pubDate>
      <guid>https://www.mfun.ink/english/post/claude-code-github-actions-ci-self-healing-pipeline/</guid>
      <description>&lt;p&gt;If your CI keeps failing and engineers keep babysitting logs, you&amp;rsquo;re paying an invisible velocity tax. A production-grade AI self-healing pipeline is not &amp;ldquo;let the agent edit anything&amp;rdquo;. It&amp;rsquo;s a controlled loop: &lt;strong&gt;attribution, patching, approval, rollback&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This post gives you a deployable baseline: Claude Code proposes a minimal fix patch, GitHub Actions enforces risk gates and regression checks, and humans only approve at high-impact checkpoints.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Nginx Reverse Proxy WebSocket Disconnects: 7 Common Traps and Reliable Fixes</title>
      <link>https://www.mfun.ink/english/post/nginx-websocket-disconnect-traps/</link>
      <pubDate>Wed, 18 Feb 2026 08:20:00 +0800</pubDate>
      <guid>https://www.mfun.ink/english/post/nginx-websocket-disconnect-traps/</guid>
      <description>&lt;p&gt;If your WebSocket keeps reconnecting every few seconds, it&amp;rsquo;s usually not your app code. In most production incidents, the root cause is an incomplete reverse-proxy chain in Nginx (or one proxy layer before it).&lt;/p&gt;
&lt;p&gt;This guide gives you a copy-paste checklist to stabilize WebSocket connections fast.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hugo Auto Deploy with GitHub Actions: Safe Config and Troubleshooting</title>
      <link>https://www.mfun.ink/english/post/github-actions-hugo-auto-deploy-safe-config/</link>
      <pubDate>Mon, 16 Feb 2026 11:59:00 +0800</pubDate>
      <guid>https://www.mfun.ink/english/post/github-actions-hugo-auto-deploy-safe-config/</guid>
      <description>&lt;p&gt;Your local &lt;code&gt;hugo&lt;/code&gt; build works, but GitHub Actions fails randomly. Classic.
The root cause is usually not the workflow syntax. It is environment drift, missing permissions, and unstable dependencies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>WSL2 &#43; Docker Network Troubleshooting: Fix DNS Timeouts and Image Pull Failures</title>
      <link>https://www.mfun.ink/english/post/wsl2-docker-network-troubleshooting/</link>
      <pubDate>Wed, 11 Feb 2026 22:50:00 +0800</pubDate>
      <guid>https://www.mfun.ink/english/post/wsl2-docker-network-troubleshooting/</guid>
      <description>&lt;p&gt;If your &lt;strong&gt;WSL2 + Docker&lt;/strong&gt; setup suddenly fails with &lt;code&gt;docker pull&lt;/code&gt; timeouts, &lt;code&gt;Temporary failure in name resolution&lt;/code&gt;, or containers that start but cannot access the internet, don&amp;rsquo;t nuke your environment yet. Most cases are recoverable in 15 minutes.&lt;/p&gt;
&lt;p&gt;This guide gives you a practical sequence: identify whether the fault is DNS, proxy/VPN, virtual NIC, or Docker daemon config—then apply the smallest fix first.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
