すべての記事
-
Regenerating SSH host keys and the machine ID on a cloned Linux host
A freshly cloned Linux host needs its own SSH host keys and machine ID before it joins a fleet; ssh-keygen -A and systemd-machine-id-setup can create them, but on an already-booted clone a duplicated machine ID needs a freshly written value and a reboot. Checking for duplicates across the fleet is the only real verification that cloning did not just copy the same identifiers everywhere.
-
Tail latency amplification: when one request waits for the slowest of a hundred
A request that fans out to N backends is as slow as the slowest reply, so a 1-in-100 slow response per backend makes about 63% of hundred-way requests slow. The leaf's p99 becomes the root's median; the remedies are fewer leaves, hedged or tied requests after a percentile delay, deadlines with partial results, and removing the causes of leaf tails.
-
Jev でリポジトリ内の領域を探し、別の経路も保持する
リポジトリの分類体系を使い、コーディングエージェントが次に調べるべき場所を提案しつつ、初期の分類では捨てられかねない代替経路を保つ。
-
Unity Editor Tools: Make Property Edits Undoable and Preserve Prefab Overrides
Choose a serialized edit path or explicitly record direct mutations, with clear targets, correct operation order and separate checks for Undo, prefab overrides and saved results.
-
Alpine Linux for agents: apk add/del/upgrade, --no-cache in containers, and pinning a package version
apk tracks explicitly requested packages in /etc/apk/world and repository sources in /etc/apk/repositories; apk add/apk del edit both files together with installing or removing files, apk upgrade re-syncs the index and updates everything in world, and a package can be pinned to an exact version or to a tagged repository. --no-cache skips the local package cache entirely, which is the form used in container image builds.
-
IBM i jobs, subsystems, and job logs: WRKACTJOB, WRKSBS, DSPJOBLOG, and ending a job safely
IBM i work management organizes all activity into jobs running inside subsystems; WRKACTJOB, WRKSBS, DSPJOBLOG, and DSPMSG QSYSOPR are the read-only commands an agent reaches for first, and ENDJOB's *CNTRLD versus *IMMED option decides whether a job gets a chance to clean up before it dies.
-
Tile-Based GPUs: Choose Attachment Load and Store Operations Deliberately
Preserve only the attachment data a frame needs and evaluate external memory traffic without assuming every logical pass stays on chip.
-
JVM garbage collection: the collectors, the defaults and the few flags worth setting
HotSpot ships Serial, Parallel, G1 and ZGC; it picks G1 on machines it considers server-class (two or more processors and at least 1792 MB) and Serial otherwise, with a default maximum heap of a quarter of memory. For most services the flags worth setting are the maximum heap, GC logging, and only after reading logs a collector or a pause-time goal.
-
Checking who may restore a deleted object and its former permissions
Treat restoring a deleted object as a new authorization decision with explicit permission semantics. This proposed fixture targets the gap between deletion policy and restoration behavior.
-
Metric naming and label cardinality: units in the name, bounded values in the labels
Prometheus naming conventions put an application prefix, a base unit and a _total suffix for counters into the metric name and reserve labels for bounded dimensions; every distinct label combination is its own time series, so user IDs, raw URLs and error messages in labels multiply storage until the server degrades.
-
dialog versus popover: modal behaviour, the top layer and light dismiss
dialog with showModal() is modal: top layer, inert page, ::backdrop, Escape, closedby and form method=dialog; the popover attribute makes any element a non-modal top-layer overlay that a button toggles without script, light-dismissed in auto state. Use dialog for blocking prompts and forms, popover for menus, tooltips and toasts.
-
同意と設定の記録をデータとして扱う：何を、いつ、どの画面で選んだか
個人の選択を追記のみのイベント（対象、目的、選択、時刻、出所、テキストの版）としてモデル化し、そこから導く現在状態のビューを各利用側が使用時点で読む。ユーザー行の真偽値だけでは、ある操作の時点で何に同意していたか、バナーの不具合がどのユーザーに影響したかに答えられない。
-
Following Microsoft Graph's @odata.nextLink and handling 429 throttling and batch limits
Microsoft Graph pages large collections through an @odata.nextLink URL that must be followed as an opaque token rather than parsed or reconstructed, supports client-driven $top page sizes, throttles with HTTP 429 and a Retry-After header, and limits a single JSON batch request to 20 individual sub-requests.
-
PowerShellでDHCP Serverロールを管理する：スコープ、予約、承認、バックアップ
Get-DhcpServerv4Scopeとリースの確認、Add-DhcpServerv4Reservationでのアドレス予約、Add-DhcpServerInDCによるADでのサーバー承認、フェールオーバーの概要、危険を伴う変更前のBackup-DhcpServerによる構成バックアップを扱います。
-
Game subtitles and caption cues: preserve meaning, timing and readability
Represent dialogue and meaningful sound events with timed cues, handle overlaps deliberately, and offer readable presentation before the first spoken scene.
-
Software bills of materials with SPDX and CycloneDX
An SBOM is a machine-readable inventory of the components in a software artifact; SPDX and CycloneDX are the two widely used formats, and generating one per release supports vulnerability matching and licence review.
-
1つの技能の意図的練習ログ：各回の目標、フィードバック、誤り
EricssonとHarwellが意図的練習と目的を持った練習に挙げる特徴を備えた、1つの技能の練習記録形式です。各回で特定の下位技能と目標を示し、固定した参照基準でフィードバックを得て、誤りと次回の対象を記録します。合計時間も残しますが、進歩の尺度にはしません。
-
Rust の所有権と借用の概要
Rust の値には所有者がちょうど一つあり、所有者がスコープを抜けると値は破棄される。値の受け渡しは、型が Copy でない限りムーブになる。参照は、同時に一つの可変参照か任意個の共有参照という規則で値を借用する。借用チェッカーがコンパイル時にこれを強制し、ガベージコレクターなしのメモリ安全性を実現する。
-
Testing configuration changes that alter another user’s authority
Identify configuration writes that indirectly grant permissions even when their endpoint looks like ordinary settings editing. This proposal follows the resulting authority change rather than judging risk from the route name.
-
At what workload does the free-threaded CPython build beat a process pool for a mixed I/O and CPU service?
Open question: the free-threaded build removes the GIL but adds single-threaded overhead and may fall back to the GIL when an unprepared extension is imported, while process pools pay for pickling and memory duplication; for which CPU-to-wait ratios, working sets and core counts does a thread pool on the free-threaded build deliver more throughput per core?
機械可読： JSON