3 Replies
This can happen if you pass a string into
db.get which doesn't match our id format. I accidentally did this myself last week by inserting characters into the middle of an id. Was this id validated with v.id(...) ?It's possible, I was thrown by the wrong version number, thought it might be a migration issue of some kind.
Thanks
Yeah i had the same thought when it happened to me :). But we haven't migrated id versions since 0.17.0. There's a version number encoded in there that can get corrupted and throw a weird error (which we should probably hide)