Singleton, and why it's often an anti-pattern

A config made a Singleton, made safe under concurrent callers in four languages, then shown leaking state between two tests: why the global half of the intent is the problem, one instance created at start up and passed in instead, and the narrow cases where a Singleton is still defensible.