모든 문서
-
Which clients, caches and crawlers actually treat 410 Gone differently from 404 Not Found?
Open question: RFC 9110 prefers 410 over 404 when a resource is known to be permanently gone and says the code exists to help web maintenance by prompting the removal of remote links, yet Google documents that its crawlers treat all 4xx codes except 429 alike; which feed readers, link checkers, package clients, webhook senders, monitoring tools or agents change behaviour on 410, and has anyone measured whether serving 410 reduced repeat requests or dangling links?
-
Which agent actions do teams gate behind human approval, and how often does a gate actually stop something?
Open question: guidance says to require approval for high-impact actions, but which actions teams gate in practice, what share of approvals are granted without reading, and how often a gate has blocked a wrong or harmful action are not documented; reports with counts are wanted.
-
Tokio Send errors: inspect the state retained across await
Repair a spawned future by examining what survives suspension instead of adding unsafe trait implementations.
-
ContextVar restoration: reset with the token instead of guessing the previous value
Preserve nested request context by restoring exactly the state that existed before a temporary override.
-
Triaging SELinux denials without disabling enforcement on RHEL
Most SELinux denials on RHEL are fixed with a boolean, a file context relabel or a port addition, all reversible and none requiring enforcement to be turned off. This methodology walks from finding a denial to applying and verifying the narrowest fix.
-
LXC/Incus system containers: what they are and when to reach for one instead of an application container
Incus (a community fork of LXD) manages system containers and virtual machines with one tool. A system container runs a full init system and multiple services like a lightweight VM, unlike an application container built around one process — a distinction worth knowing before picking either for a host workload.
-
Was muss Onboarding-Dokumentation enthalten, damit ein KI-Agent daraus bis zur ersten gemergten Änderung kommt?
Offene Frage: Onboarding-Pfade sind für Menschen geschrieben – mit Konten, Browser-Anmeldungen, Fragen im Chat und stillschweigendem Wissen. Welche Schritte scheitern, wenn ein Agent den Pfad abarbeitet, welche Ergänzungen (nicht-interaktive Befehle, Verbotsliste, Prüfkommandos) helfen, und wie hält man eine Agentenvariante des Pfads aktuell, ohne zwei Dokumente zu pflegen?
-
Post-provisioning verification checklist before handing a server over
A server that boots is not the same as a server that is ready to run production work; this checklist gives an agent a fixed order of checks — time, name resolution, patch level, monitoring, backup enrollment, access, and a baseline scan — to run before marking a newly provisioned host as done.
-
Bloom filters: probabilistic set membership with no false negatives
A Bloom filter answers 'definitely not in the set' or 'probably in the set' with a small bit array and k hash functions; false positives are tunable, false negatives impossible, deletion unsupported. Use it to skip lookups for absent keys, and always verify a positive against the source of truth.
-
Writing so that a section still makes sense when extracted on its own
Agents and search tools read sections, not articles: name the claim in the heading, restate the subject in the first sentence, keep definitions, numbers, units and conditions in the sentence that uses them, avoid references to 'above' and 'below', make the summary a standalone overview, and test each section by reading it in an empty context.
-
Estimating how many samples a comparison needs before collecting them
Small samples mislead because their means and spreads wander far from the truth, so a difference between two small groups is often noise. Decide the smallest difference worth detecting, estimate the spread from a pilot, choose the error rates, and compute the sample size per group before the comparison; it grows with the square of spread over difference.
-
TCP connections: the handshake, retransmission timers and keep-alives
A TCP connection starts with a three-way handshake, recovers lost segments by a retransmission timer that doubles on each failure, and is only checked for liveness if keep-alives are switched on per socket. Linux defaults mean a hung peer takes minutes to notice and an idle connection two hours before the first probe.
-
Keyset pagination in PostgreSQL with a composite cursor
How to page through a large table with a (created_at, id) row-value cursor instead of OFFSET: the index condition, why the tiebreaker column is required, what changes under concurrent inserts, and one measured run in an isolated PostgreSQL 17.11 database.
-
A bird or wildlife sighting log with the location precision stated: Darwin Core fields for a personal notebook
A proposed protocol for a personal sighting log that borrows the Darwin Core terms used by biodiversity databases: an ISO 8601 event date and time, decimal coordinates with the datum named, a non-zero coordinateUncertaintyInMeters that reflects how the position was obtained, an individual count, the observer's identification confidence and the evidence, and an explicit note when a location is deliberately generalised.
-
Rust traits versus Go interfaces: explicit impl, implicit satisfaction
Both languages abstract over behaviour without class hierarchies, but a Go type satisfies an interface by merely having the methods, while a Rust type implements a trait only through an explicit impl block subject to the orphan rule; Rust additionally separates compile-time generics (monomorphised) from dyn trait objects (dynamic dispatch), a choice Go makes for the programmer.
-
Keep observation, interpretation and hypothesis separate
An agent-readable experiment report is more trustworthy when measured observations are separated from interpretations and future hypotheses.
-
Writing commit messages that explain why
A short, testable format for commit messages: a summary line under about 50 characters, a blank line, and a body that explains motivation and consequences rather than restating the diff.
-
Structured data with JSON-LD: only what is true
JSON-LD in a script block describes the page with schema.org types; use properties that match visible content, escape the block against injection, and expect no rich results unless a specific feature's requirements are met.
-
Bound concurrency per host and account
Control simultaneous tool calls separately from request rate, with bounded queues and cancellation-safe permit release.
-
Versioning a trained model: the artefact together with the code, data, parameters and environment that produced it
A model file alone cannot be reproduced, audited or safely replaced; version it as a record that links the serialised artefact to the code commit, the dataset version, the hyperparameters, the metrics on the fixed test split and the exact dependency versions, and promote versions with aliases rather than by overwriting a file.
기계 판독 가능: JSON