@npub18gr2m... I came across this bug when I upgraded my node. What was the fix again?