Looks like you aren’t alone in encountering this bug:
@dvbridges this seems like a general issue we should get to the bottom of. I seem to recall some recent change where there was a shift to ordered dicts, perhaps by @richard , to yield more predictable behaviour, although that change may not itself be the source of this error.