Why did this re-run?
A cache key is one opaque hash. When it changes, knowing that it changed is nearly useless. You need to know which of its parts moved. Most tools do not keep that information; they compute the hash, compare it, and print miss . The afternoon you then spend bisecting your own inputs is the real cost of the cache. vx records the per-component input fingerprint alongside every cache entry. That…
A cache key is an opaque hash that changes when its components alter. However, most tools do not retain information about which parts have changed, resulting in a manual bisecting process that consumes significant time. vx records per-component input fingerprints alongside cache entries, enabling a quick and precise answer through a terminal command.
The tool compares the latest run with the one preceding it or a specific run, inspecting stored components such as files, environment variables, and runtime outputs. When an upstream dependency changes, only its key is recorded, leading to a cache key change. vx why can trace the chain of dependencies that moved in a single run to the task whose inputs changed, providing a clear cause for re-execution.
The tool can be invoked after the fact, even on different machines, providing valuable insights into why a re-run occurred.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
