全部文章
-
日志、指标与追踪:如何选择信号
日志记录离散事件,指标随时间聚合数值测量,追踪则跟随单个请求穿过多个服务。OpenTelemetry 将三者标准化,使它们可以相互关联。
-
Users, roles and RBAC on Solaris: why root is a role by default and how pfexec replaces sudo
Oracle Solaris implements privileged administration through RBAC rights profiles assigned to users or roles, and configures root as a role rather than a directly loginable user by default. pfexec, not sudo, is the native command for running a single privileged command under an assigned profile.
-
The JavaScript event loop: tasks, microtasks and rendering
JavaScript runs one job at a time; the HTML event loop takes a task, then drains the whole microtask queue (promise reactions, queueMicrotask) before the next task or a rendering opportunity. Long synchronous work and endless microtask chains block input and painting.
-
Datensicherungen wirklich prüfen: die Rücksicherungsprobe
Eine Sicherung ist erst dann eine Sicherung, wenn eine Rücksicherung in eine leere Umgebung gelungen und geprüft worden ist. Das Vorgehen: Erwartung festlegen, allein aus der Sicherung wiederherstellen, Vollständigkeit und Funktion messen, Dauer notieren, Befund ablegen und den Termin für die nächste Probe setzen.
-
Serial and out-of-band consoles for servers that keep access when the network is down
A serial console (console=ttyS0,115200 plus a getty on the line), a cloud provider's serial console feature, or IPMI/BMC Serial-over-LAN each give an administrator a way into a server that has no working network stack — the situation a purely SSH-based access plan cannot survive.
-
CIS Benchmarks and DISA STIGs as a hardening baseline: what they are and how to apply them selectively
CIS Benchmarks and DISA STIGs are two independently maintained sets of configuration recommendations; both offer selectable profile levels rather than one fixed target. Applying a profile wholesale without recording exceptions is a common way hardening work breaks a production service.
-
Routing all interrupts to one rotating person raises the rest of the team's uninterrupted time
Hypothesis: a team that assigns tickets, questions and operational requests to a single rotating interrupt handler, and stops distributing them across everyone, increases the median length of uninterrupted work blocks for the other members without lengthening interrupt response times beyond the agreed target; a proposed measurement.
-
服务端请求伪造:抓取用户提供的 URL
服务器抓取用户提供的 URL 时,可能被引向内部服务和元数据端点。应为协议方案和主机建立允许列表,解析并检查地址,禁止重定向到私有地址范围,并优先考虑完全不发起抓取。
-
优化前先做性能剖析
为了提速而修改代码前,先用性能剖析器测量时间实际上花在哪里;对热点的大多数猜测都是错的,未经测量的优化只会增加复杂性而没有收益。
-
有符号算术溢出:更改优化前先记录编译器契约
发布构建与调试构建行为不同时,将算术要求与 GCC 溢出标志分开考虑。
-
Token bucket, leaky bucket and sliding window: how rate-limiter algorithms differ
Fixed windows are cheap but let twice the limit through at a boundary; sliding logs are exact but store every timestamp; sliding-window counters approximate in constant memory; token buckets allow bursts up to the bucket size at a fixed refill rate; leaky buckets smooth output by delaying. nginx and Envoy document the last two.
-
代理需要怎样的 API 描述
代理读取机器描述而非自然语言说明:从一个发现文档出发的稳定链接、带类型的响应、文档化的错误和重试信号、幂等性,以及对不可用功能的明确说明。
-
端到端传递请求 ID:入口、日志、下游调用与响应
在入口生成请求标识符(nginx 提供 $request_id,即 16 个随机字节的十六进制表示),通过请求头传给应用,保存在请求作用域上下文中,让每条日志和每次出站调用都携带它,并在响应中返回,以便将用户反馈匹配到该请求经过的每个服务的日志;已有追踪时,使用 W3C trace ID 作为这一标识符。
-
Test data builders with defaults reduce test breakage when a domain object changes
Hypothesis: suites that build objects through builders, where every field has a valid default and a test sets only the fields it asserts on, need fewer test edits per schema or constructor change than suites relying on shared fixtures or object mothers with canned instances.
-
Validating email addresses: what a syntax check can and cannot tell you
RFC 5321 caps the local-part at 64 octets and a path at 256; the HTML standard deliberately uses a simpler grammar than RFC 5322 for input type=email; internationalised addresses need SMTPUTF8 end to end. Check syntax and lengths, look up MX at signup, confirm ownership with a message, and never 'correct' an address automatically.
-
Decomposing a compound judgment into atomic questions for a decision model raises agreement with human labels compared with one multi-factor question
Vendor guidance for decision models says to ask one specific thing per question and combine in code; this hypothesis states that prediction as a measurable claim: for judgments that weigh several independent factors, the decomposed form agrees more often with human labels than a single question whose criteria describe the combination.
-
Recording the execution target before interpreting a diagnostic result
Establish which process, checkout, service instance, or database a diagnostic command actually reached before applying its result to the user’s reported problem.
-
Combining baked lightmaps with lighting probes for moving objects
Plan surface UVs and spatial lighting samples together so static scenery and dynamic objects share a coherent baked lighting setup.
-
Barrierefreiheit: die vier WCAG-Grundsätze praktisch angewendet
Die WCAG 2.2 ordnen alle Erfolgskriterien vier Grundsätzen zu: wahrnehmbar, bedienbar, verständlich, robust. Wer pro Grundsatz die häufigsten Verstösse kennt (fehlende Textalternativen, Tastaturfallen, zu wenig Kontrast, unbeschriftete Felder, zu kleine Ziele), findet viele Barrieren ohne Spezialwerkzeug; Stufe AA ist das übliche Ziel.
-
Ren'Py Dialogue Branches: Connect Choices, Story Variables and Return Paths
Use menus to select local story blocks, labels to organize destinations, and explicit call or jump semantics so branches preserve their consequences and reconnect intentionally.
机器可读: JSON