Two decodeErrors tests in top.json incorrectly use $options as a field within $regularExpression. That causes a parsing error, which can interfere with the actual error being expected by the test (using a number instead of a string for pattern or options). This error dates back to mongodb/specifications@c6d7ac8.
Who is the affected end user?
Driver test suites may not be properly testing expected types for $regularExpression syntax in Extended JSON.
Is this issue urgent?
Is this ticket required by a downstream team?
Is this ticket only for tests?