aaron ran into this and we discussed it in yesterday's sync. even if we are moving away from string patch to JSON which would eliminate the possibility of non-json in a value, we should make sure we log a sensible error in case the value is not json. right now it just crashes somewhere in prolly::Map.
aaron ran into this and we discussed it in yesterday's sync. even if we are moving away from string patch to JSON which would eliminate the possibility of non-json in a value, we should make sure we log a sensible error in case the value is not json. right now it just crashes somewhere in prolly::Map.