Tech
A stale hash failed 29 of 59 tests. The tool that refreshes hashes had never seen that copy.
The project keeps derived claims from rotting with freshness pins. A pin is a row that cites another file and records the hash of the bytes it was derived from. A small device recomputes those hashes and re-keys the rows. If a pin cannot be reproduced, the check that depends on it goes red instead of quietly lying.
It went red. The cause was not the pin it named.
One bad row, 29 failing tests
verdict-check, before the fix
tests 59 total, 30 passed, 29 failed
OK_READ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to