Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-2139

Regex decoding error tests in top.json have unexpected, invalid syntax

XMLWordPrintableJSON

    • Type: Icon: Spec Change Spec Change
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.12.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Downstream changes: drivers should sync their BSON corpus spec tests to mongodb/specifications@5fad277. Two regex tests within top.json's decodeErrors array have changed.

      Summary

      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.

      Motivation

      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?

      No.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Yes.

            Assignee:
            qingyang.hu@mongodb.com Qingyang Hu
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: