<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Entry Examples——模具行业从业者必备知识手册]]></title><description><![CDATA[<p dir="auto">&lt;h2&gt;Entry Examples&lt;/h2&gt;</p>
<p dir="auto">&lt;p&gt;Concrete examples of well-formatted entries with all fields.&lt;/p&gt;</p>
<p dir="auto">&lt;h3&gt;Learning: Correction&lt;/h3&gt;</p>
<p dir="auto">&lt;pre&gt;&lt;code&gt;</p>
<h2>[LRN-20250115-001] correction</h2>
<p dir="auto"><strong>Logged</strong>: 2025-01-15T10:30:00Z<br />
<strong>Priority</strong>: high<br />
<strong>Status</strong>: pending<br />
<strong>Area</strong>: tests</p>
<h3>Summary</h3>
<p dir="auto">Incorrectly assumed pytest fixtures are scoped to function by default</p>
<h3>Details</h3>
<p dir="auto">When writing test fixtures, I assumed all fixtures were function-scoped.<br />
User corrected that while function scope is the default, the codebase<br />
convention uses module-scoped fixtures for database connections to<br />
improve test performance.</p>
<h3>Suggested Action</h3>
<p dir="auto">When creating fixtures that involve expensive setup (DB, network),<br />
check existing fixtures for scope patterns before defaulting to function scope.</p>
<h3>Metadata</h3>
<ul>
<li>Source: user_feedback</li>
<li>Related Files: tests/conftest.py</li>
<li>Tags: pytest, testing, fixtures</li>
</ul>
<hr />
<p dir="auto">&lt;/code&gt;&lt;/pre&gt;</p>
<p dir="auto">&lt;h3&gt;Learning: Knowledge Gap (Resolved)&lt;/h3&gt;</p>
<p dir="auto">&lt;pre&gt;&lt;code&gt;</p>
<h2>[LRN-20250115-002] knowledge_gap</h2>
<p dir="auto"><strong>Logged</strong>: 2025-01-15T14:22:00Z<br />
<strong>Priority</strong>: medium<br />
<strong>Status</strong>: resolved<br />
<strong>Area</strong>: config</p>
<h3>Summary</h3>
<p dir="auto">Project uses pnpm not npm for package management</p>
<h3>Details</h3>
<p dir="auto">Attempted to run <code>npm install</code> but project uses pnpm workspaces.<br />
Lock file is <code>pnpm-lock.yaml</code>, not <code>package-lock.json</code>.</p>
<h3>Suggested Action</h3>
<p dir="auto">Check for <code>pnpm-lock.yaml</code> or <code>pnpm-workspace.yaml</code> before assuming npm.<br />
Use <code>pnpm install</code> for this project.</p>
<h3>Metadata</h3>
<ul>
<li>Source: error</li>
<li>Related Files: pnpm-lock.yaml, pnpm-workspace.yaml</li>
<li>Tags: package-manager, pnpm, setup</li>
</ul>
<h3>Resolution</h3>
<ul>
<li><strong>Resolved</strong>: 2025-01-15T14:30:00Z</li>
<li><strong>Commit/PR</strong>: N/A - knowledge update</li>
<li><strong>Notes</strong>: Added to <a href="http://CLAUDE.md" rel="nofollow ugc">CLAUDE.md</a> for future reference</li>
</ul>
<hr />
<p dir="auto">&lt;/code&gt;&lt;/pre&gt;</p>
<p dir="auto">&lt;h3&gt;Learning: Promoted to CLAUDE.md&lt;/h3&gt;</p>
<p dir="auto">&lt;pre&gt;&lt;code&gt;</p>
<h2>[LRN-20250115-003] best_practice</h2>
<p dir="auto"><strong>Logged</strong>: 2025-01-15T16:00:00Z<br />
<strong>Priority</strong>: high<br />
<strong>Status</strong>: promoted<br />
<strong>Promoted</strong>: <a href="http://CLAUDE.md" rel="nofollow ugc">CLAUDE.md</a><br />
<strong>Area</strong>: backend</p>
<h3>Summary</h3>
<p dir="auto">API responses must include correlation ID from request headers</p>
<h3>Details</h3>
<p dir="auto">All API responses should echo back the X-Correlation-ID header from<br />
the request. This is required for distributed tracing. Responses<br />
without this header break the observability pipeline.</p>
<h3>Suggested Action</h3>
<p dir="auto">Always include correlation ID passthrough in API handlers.</p>
<h3>Metadata</h3>
<ul>
<li>Source: user_feedback</li>
<li>Related Files: src/middleware/correlation.ts</li>
<li>Tags: api, observability, tracing</li>
</ul>
<hr />
<p dir="auto">&lt;/code&gt;&lt;/pre&gt;</p>
<p dir="auto">&lt;h3&gt;Learning: Promoted to AGENTS.md&lt;/h3&gt;</p>
<p dir="auto">&lt;pre&gt;&lt;code&gt;</p>
<h2>[LRN-20250116-001] best_practice</h2>
<p dir="auto"><strong>Logged</strong>: 2025-01-16T09:00:00Z<br />
<strong>Priority</strong>: high<br />
<strong>Status</strong>: promoted<br />
<strong>Promoted</strong>: <a href="http://AGENTS.md" rel="nofollow ugc">AGENTS.md</a><br />
<strong>Area</strong>: backend</p>
<h3>Summary</h3>
<p dir="auto">Must regenerate API client after OpenAPI spec changes</p>
<h3>Details</h3>
<p dir="auto">When modifying API endpoints, the TypeScript client must be regenerated.<br />
Forgetting this causes type mismatches that only appear at runtime.<br />
The generate script also runs validation.</p>
<h3>Suggested Action</h3>
<p dir="auto">Add to agent workflow: after any API changes, run <code>pnpm run generate:api</code>.</p>
<h3>Metadata</h3>
<ul>
<li>Source: error</li>
<li>Related Files: openapi.yaml, src/client/api.ts</li>
<li>Tags: api, codegen, typescript</li>
</ul>
<hr />
<p dir="auto">&lt;/code&gt;&lt;/pre&gt;</p>
<p dir="auto">&lt;h3&gt;Error Entry&lt;/h3&gt;</p>
<p dir="auto">&lt;pre&gt;&lt;code&gt;</p>
<h2>[ERR-20250115-A3F] docker_build</h2>
<p dir="auto"><strong>Logged</strong>: 2025-01-15T09:15:00Z<br />
<strong>Priority</strong>: high<br />
<strong>Status</strong>: pending<br />
<strong>Area</strong>: infra</p>
<h3>Summary</h3>
<p dir="auto">Docker build fails on M1 Mac due to platform mismatch</p>
<h3>Error</h3>
<p dir="auto">&lt;/code&gt;&lt;/pre&gt;<br />
&lt;p&gt;error: failed to solve: python:3.11-slim: no match for platform linux/arm64&lt;/p&gt;<br />
&lt;pre&gt;&lt;code&gt;</p>
<h3>Context</h3>
<ul>
<li>Command: <code>docker build -t myapp .</code></li>
<li>Dockerfile uses <code>FROM python:3.11-slim</code></li>
<li>Running on Apple Silicon (M1/M2)</li>
</ul>
<h3>Suggested Fix</h3>
<p dir="auto">Add platform flag: `doc</p>
<hr />
<p dir="auto">新手建议收藏，老手欢迎指点。<br />
&lt;/code&gt;&lt;/pre&gt;</p>
]]></description><link>https://forum.mj7.cn/topic/7122/entry-examples-模具行业从业者必备知识手册</link><generator>RSS for Node</generator><lastBuildDate>Fri, 02 Oct 2026 14:42:28 GMT</lastBuildDate><atom:link href="https://forum.mj7.cn/topic/7122.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 19 Apr 2026 21:35:22 GMT</pubDate><ttl>60</ttl></channel></rss>