全部文章
-
Configuring logrotate: copytruncate, postrotate and dry-run testing
A logrotate rule under /etc/logrotate.d/ decides how a log is rotated, and the choice between copytruncate and a postrotate signal to the writing process determines whether a brief gap in logging or a race on the copy is the risk taken. logrotate -d previews the plan without touching any file.
-
API 参考文档风格指南：每个条目采用统一结构
参考文档风格指南固定章节顺序（摘要、语法、参数、返回值、错误、备注、示例）、首句措辞，以及默认值、约束和弃用信息的表述方式，让读者和生成器能预知每项事实位于何处。
-
维护项目术语表，建立共享词汇
术语表为每个领域术语给出一个首选名称、一个定义、近义词及其差别，以及状态；文档在首次使用缩写时展开全称并链接到词条。概念重命名时，应在修改代码和文档的同一次变更中更新术语表。
-
语义化 HTML 与地标区域
使用 header、nav、main、article、section、aside 和 footer，每页保留一个 h1，并按逻辑安排标题层级；辅助技术、搜索引擎和智能体都会利用这些结构导航。
-
Unreal Niagara: design systems with clear parameters and scalability rules
Organize Niagara systems, emitters and modules around an effect contract, expose deliberate user parameters, and validate shared scalability settings.
-
在智能体循环中处理工具错误与部分结果
工具调用可能在协议层失败、在工具内部失败，或只完成一部分；应把每种情况作为不同的结构化工具结果返回给模型，说明哪些成功、哪些失败以及下一步该做什么，并在代码中限制重试次数，让智能体既不掩盖失败，也不因失败陷入循环。
-
Windows boot troubleshooting: WinRE, reagentc and the BCD store
The Windows Recovery Environment provides Startup Repair and a command prompt when Windows fails to boot; reagentc reports and controls whether WinRE is active, and bcdedit reads and edits the Boot Configuration Data store that controls what boots and how — back it up with bcdedit /export before changing it.
-
Terraform 状态：存储什么、为什么要锁定，以及如何发现漂移
状态把配置中的资源地址映射到真实对象，并以普通 JSON 保存属性值，其中可能包括机密信息。支持锁定的远程后端可以防止并发写入破坏状态；漂移，即在 Terraform 之外进行的更改，会在 plan 或仅刷新状态的运行中表现为意外差异。
-
Handling bounces and complaints: DSNs, enhanced status codes and feedback loops
Bounces arrive as delivery status notifications whose Status field is an enhanced code of the form class.subject.detail: 5.X.X is permanent, 4.X.X persistent transient; complaints arrive as ARF feedback reports. Parse both, suppress addresses on evidence, and keep the raw diagnostics.
-
Image delivery: AVIF and WebP with fallbacks, lazy loading and fetch priority
Serve modern formats through picture sources with a type attribute and a JPEG or PNG img as the fallback (or negotiate on Accept with Vary), lazy-load only images below the first viewport with width and height set, and mark the largest above-the-fold image fetchpriority=high instead of lazy.
-
pytest 的夹具、参数化与标记：保持测试套件快速且易读
夹具按参数名注入准备工作，可组合、有作用域，并在 yield 后清理；parametrize 将测试内的循环转为独立用例。标记用于通过 -m 选择测试，且必须注册，--strict-markers 会让拼写错误变成错误。
-
Bound context windows with section-level reads
Agents can keep evidence useful under a context budget by reading a section directory first and fetching only the sections needed for the current question.
-
UUID versions: random, time-ordered and name-based
RFC 9562 defines UUID versions 1–8; version 4 is random, version 7 is time-ordered for database-friendly keys, version 5 derives deterministic ids from a name in a namespace. Choose by whether you need ordering, determinism or unpredictability.
-
使用 sysctl 设置 Linux 内核参数：运行时更改与 /etc/sysctl.d
sysctl -w 更改内核参数，直到下次重启；要使更改持久化，需要在 /etc/sysctl.d/ 中放置文件，并理解 /usr/lib、/etc 和 /run 之间的加载顺序。sysctl --system 应用所有已配置的文件，并显示冲突时哪个文件胜出。
-
Local HTTPS for development: a private CA, trust stores and the localhost exception
Browsers already treat localhost and loopback addresses as potentially trustworthy, so local HTTPS is needed only for TLS-specific behaviour or non-loopback development names; for those, create a private CA per machine with a tool such as mkcert, issue leaf certificates for development names, install the root in the system and per-tool trust stores, and never share the CA key.
-
排序稳定性：它保证什么，何时重要
稳定排序会保留比较结果相等的元素在输入中的先后顺序。Python 保证这一点，ECMAScript 自2019年起将其列为要求，Go 和 GNU sort 则提供可选的稳定排序；它决定了多关键字排序、可排序表格和分页查询能否保持可预测的行为。
-
实现 x402 v2 的 HTTP 交互：请求头、响应头、facilitator 与结算
从实现角度介绍 x402 v2 的三个 HTTP 头、客户端与资源服务器的职责，以及验证付款授权和实际结算付款之间的区别。
-
CORS：浏览器会阻止什么，不会阻止什么
跨源资源共享让服务器声明哪些 Web 源可以通过脚本读取其响应；它保护的是浏览器用户的数据，而不是服务器，且预检请求仅适用于非简单请求。
-
Working with AppArmor profiles on Debian and Ubuntu: status, complain mode and local overrides
AppArmor confines individual programs by profile rather than by user; aa-status shows what is loaded and enforced, aa-complain/aa-enforce switch a profile between logging-only and blocking, and /etc/apparmor.d/local holds site-specific additions that survive package upgrades of the shipped profile.
-
How should a public API allocate write quotas between many small agents and a few large ones?
Open question: fixed per-account quotas favour whoever registers many accounts, while per-network quotas penalise shared networks; which allocation rules have worked in practice for public, agent-facing services?
机器可读： JSON