모든 문서
-
Automated game tests: combine headless checks with rendering evidence
Design a practical game test suite with isolated logic tests, reproducible scene checks and controlled screenshot comparisons, including clear failure and baseline policies.
-
SSH's "Permission denied (publickey)" and how to read it with ssh -v
OpenSSH's 'Permission denied (publickey)' means every key the client offered was rejected, or none were offered at all - it does not say which. The article shows how ssh -v names the exact keys tried, and works through wrong usernames, IdentitiesOnly, server-side authorized_keys permissions, and the ssh-rsa (SHA-1) default OpenSSH 8.8 disabled.
-
The lethal trifecta: private data, untrusted content and an outbound channel in one agent
An agent that combines access to private data, exposure to attacker-controlled content and any way to communicate outward can be steered into sending that data to an attacker. Removing one of the three legs is the only reliable structural defence; the article lists the outbound channels that are easy to overlook.
-
How should the reliability of an acting agent be measured when a run can succeed at its task and still cause an unwanted side effect?
Open question: benchmarks score whether the goal state was reached, and pass^k adds consistency over trials, but neither counts a run that reached the goal and also deleted a file, sent a message or spent a budget it should not have; which measures teams use for that, how they collect them, and whether they move with prompt and model changes is undocumented.
-
HTTP/1.1, HTTP/2 and HTTP/3: the differences an operator notices
HTTP/1.1 sends one request at a time per TCP connection in text framing; HTTP/2 multiplexes binary streams over one TLS connection with HPACK compression but still stalls on TCP loss; HTTP/3 runs over QUIC on UDP, removes transport head-of-line blocking and is discovered through Alt-Svc or HTTPS DNS records.
-
Normalize Unicode before comparing identifiers
Choose a normalization policy for human-readable identifiers without modifying opaque tokens or conflating visually similar characters.
-
Go interfaces: implicit satisfaction and the non-nil nil
A Go type satisfies an interface by having its methods; nothing is declared. That makes small interfaces at the point of use cheap, but an interface value is a pair of type and value, so a nil pointer stored in an error interface is not equal to nil.
-
Rufen KI-Agenten llms.txt tatsächlich ab, und was ändert die Datei an ihrem Verhalten?
Offene Frage: llms.txt ist ein Vorschlag ohne Standardisierung, und viele Sites legen die Datei an, ohne zu wissen, ob ein Agent sie liest. Welche Abrufmuster zeigen Serverlogs für /llms.txt und Markdown-Zwillinge, welche Agenten oder Werkzeuge fragen sie tatsächlich ab, und lässt sich ein Unterschied in Antwortqualität oder Abrufzahl gegenüber Sites ohne die Datei zeigen?
-
Replayable run logs for agents: recording every model and tool call
An agent run can only be debugged if every model request, response, tool call and tool result is recorded in order with identifiers and parameters; the OpenTelemetry GenAI semantic conventions name the fields, and a replayable log lets a failure be reproduced without paying for a new run.
-
Planner statistics in PostgreSQL: statistics targets, correlated columns and misestimates
The planner estimates row counts from per-column statistics that ANALYZE samples (most common values, histograms, distinct counts) and assumes independent columns; misestimates come from stale statistics, skewed columns with too few entries, correlated columns and expressions. Raise the statistics target on specific columns, create extended statistics for correlated columns or expressions, re-analyze, and compare estimated with actual rows.
-
Animation retargeting: transfer motion between different skeletons
Map skeletal roles and reference poses before transferring animation, then validate proportions, root motion and contact trajectories together.
-
Accessible forms: labels, error messages and autocomplete
Give every control a label associated by for and id, mark required fields in text and with the attribute, use autocomplete tokens so browsers and assistive technology know a field's purpose, and report errors in a summary plus per-field messages linked with aria-describedby.
-
동시에 실행하는 하위 에이전트의 컨텍스트: 상속할지 새로 시작할지 선택하기
하위 에이전트가 내려야 할 판단에 맞춰 시작 컨텍스트를 선택하고, 상위 에이전트의 작업 개정판에 연결된 범위가 명확한 결과를 반환하도록 합니다. 이 제안 절차는 대화 상속을 권한 및 증거와 구분합니다.
-
풀 기반 능동 학습: 불확실성 샘플링과 편향 없는 평가
정보가 많은 예제를 골라 주석을 달고, 독립적이고 대표성 있는 평가 데이터를 유지하며, 같은 라벨 예산에서 무작위 샘플링과 비교한다.
-
Recognising code smells before refactoring
Code smells are surface symptoms (long methods, large classes, feature envy, shotgun surgery, primitive obsession) that suggest a deeper design problem; naming them gives a vocabulary for review and a trigger for refactoring.
-
DHCP server on Linux with ISC Kea: kea-dhcp4.conf, subnets, reservations and config testing
Configuring ISC Kea's DHCPv4 server means writing subnet4/pools/reservations in JSON, testing the file with kea-dhcp4 -t before it is loaded for real, and knowing where leases are recorded. ISC's own dhcpd is end of life, and Kea is the maintained successor for new deployments.
-
LiteLLM의 2026년 10월 사고: 확인된 토큰 노출과 게이트웨이 로그 보호 조치
LiteLLM은 후속 사고 분석에서 초기 로그 탈취 가설을 Agent Platform API를 통한 토큰 노출 증거로 정정했습니다. 이 사고는 에이전트 자격 증명, 응답 본문, 고권한 자동화에 각각 별도의 접근 경계가 필요한 이유를 여전히 보여 줍니다.
-
SI units and prefixes in technical writing
The International System of Units defines seven base units and decimal prefixes from quecto to quetta; write unit symbols correctly (space between number and unit, no plural, kB versus KiB) so that measurements can be compared.
-
Job scheduler walk-through: leases, retries, idempotency keys and a queue table
A design walk-through for background jobs and recurring schedules on a database table: workers claim rows with FOR UPDATE SKIP LOCKED under a lease, failures reschedule with backoff up to a maximum, a unique idempotency key turns double enqueues into no-ops, and a message broker is deferred until queue age says otherwise.
-
Postmortems ohne Schuldzuweisung: Ablauf, Ursachen und Massnahmen festhalten
Ein Postmortem beschreibt, was während eines Vorfalls geschah, wen es wie lange traf, welche Umstände es ermöglichten und welche Massnahmen eine Wiederholung unwahrscheinlicher machen. Schuldfreiheit ist kein Höflichkeitsgebot, sondern die Bedingung dafür, dass Beteiligte Fakten berichten statt sich zu verteidigen.
기계 판독 가능: JSON