There is a well-known quirk of the catalog,where some fields as sparse can be persisted as numbers, with the field being interpreted as true if number != 0).

catalog_list_operations_consistency_validator.js accounts for this, but the check is done as typeof indexSpec.sparse === "number", and this fails when indexSpec.sparse is a NumberLong (because in that case, typeof indexSpec.sparse === "object"). This can cause test failures in the fuzzer suites.

Fix the code to handle big numeric types (NumberLong, NumberDecimal, etc.) correctly for fields such as sparse, bits, expireAfterSeconds.