WATCH AT EASE · PRACTICAL GUIDE
Answers to everyday questions, checked for current relevance.
265–288 / 365
Do not begin with prune, remove, unlock, repair, or force. Map every worktree path, branch owner, backlink, lock, dirty state, operation, and dry-run result first.
Do not make SQLSTATE 55006 disappear before you know who owns it. Capture a read-only, cluster-bound ledger of sessions, prepared transactions, logical replication objects and visibility limits, then repeat the snapshot to catch reconnect races before any destructive step.
A no-signal message does not prove the dock is dead. Record which part of the display path still works, change one variable at a time, and keep mode-specific fixes on the correct branch.
Do not begin with --force, prune, or a daemon restart. Bind the error to the exact Docker context, inventory every mount owner—including stopped containers and Swarm services—and preserve the evidence first.
A subtitle that drifts only after a seek, resume, direct stream, or transcode may not be a bad subtitle file. Preserve the original, test the same three dialogue cues across local and Jellyfin playback, and record the path that creates the mismatch before you edit anything.
A tested read-only collector joins the PVC, PV, Pods, StorageClass and VolumeAttachments into one evidence ledger before any destructive storage action.
A read-only audit separates Docker objects, the WSL guest filesystem and the Windows VHDX before any destructive cleanup or offline compaction.
Build a read-only evidence ledger for Git’s ownership warning before changing permissions or adding a safe.directory exception.
Preserve dirty work, map Git's two path records, choose the correct repair branch, and verify both directions before prune or removal.
Inventory a quiet local vault copy, match only documented conflict filenames and compare exact Markdown bytes. The read-only tool flags missing originals and unsupported names; matching hashes never approve deletion.
Preserve the evidence, classify restic’s documented check result, and map the least destructive next step before index or snapshot repair.
A local Bitwarden ZIP audit inventories and hashes the files that are present. The archive cannot prove by itself that every server-side attachment was exported. Use this offline audit to catch structural problems, compare with a separately saved baseline and decide when deletion or migration must remain on hold.
A successful ZIP download can still contain LFS pointers. Use a trusted commit's pointer to check one exact archive member's uncompressed bytes, and keep a one-file match separate from a complete repository backup.
A read-only CSV ledger can show what survived without changing the only profile copy you may have.
A download loop is a boundary failure, not proof that every server install is disposable. Preserve one complete log, bind it to the exact VS Code commit, test download, unpack, startup and tunnel separately, then repair only the boundary you can prove is broken.
A successful command is not the same as complete verification. Prove the crypt topology and backend hash capability, choose cryptcheck or download comparison deliberately, capture every report class, and keep errors or unsupported objects out of the verified total.
Separate download timestamps, embedded tags and sidecar dates in a read-only pilot report; a filename match is not permission to rewrite metadata.
An orphan warning does not prove a container is disposable. Confirm the effective Compose project, inspect ownership labels and data mounts, distinguish renamed services from project-name collisions and one-off runs, then choose the smallest safe action.
Pointer text in a cloned working tree is a symptom, not a root cause. Preserve local changes, identify the exact LFS object, then separate attribute and filter setup from download, authentication, local-object and checkout failures before you reclone or reset anything.
A silent yt-dlp result does not automatically mean the download failed. Preserve the file and verbose log, inspect the streams that actually exist, then separate a video-only selection from a skipped merge or a playback-compatibility problem before downloading anything again.
The warning is a safety stop, not a prompt to rebuild a hidden folder blindly. Use this read-only preflight to distinguish an unmounted drive, a moved path, cleanup deletion and a permission failure before you let synchronization resume.
Use a tested read-only script to page a local Plex Media Server history endpoint, preserve per-user event records and flag an export that may be incomplete.
Build a read-only attachment-path audit, separate linked files from stored copies, and test a small verified repair before changing Zotero paths in bulk.
If a Steam Deck dock works without its power supply but loses display, Ethernet, USB or charging when power is attached, preserve that reversal. A two-state matrix can separate a display-only branch from a dock-wide power or USB-C path before you erase settings or replace hardware.