Bad data that looks like it should be good data about maxmind-db HOT 3 CLOSED

I'm sorry, I was debugging this and noticed that "MaxMind-DB-test-decoder.mmdb" and "MaxMind-DB-test-pointer-decoder.mmdb" were switched around (I've edited the first post to correct it.)

In any case: the parser can process those databases fine, so it's clearly an issue with the validator.

Nothing to see here.

Thanks! Sorry for the bother, I should have checked this first 🙃

from maxmind-db.

Those databases should be valid. You can see what is in them in the script that generates them. I haven't looked at the database in a hexeditor, but I did run our mmdbverify tool against them, which should return an error if there is a non-string key in a map.

Looking at the data inserted in the database, it looks like 1 and 7 show up in an array, not a map. Arrays can contain uint32 values. Are you sure about the type of the container?

from maxmind-db.

I was thinking a bit more about this, and I was wondering if perhaps you are not taking into account the size of the array properly. Based on the description, it sounds like the array elements might be getting added into the map that contains the array rather than the array itself.

from maxmind-db.