MongoDB 7.0.26 -> 28 broke QA test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • patch-next
    • Affects Version/s: None
    • Component/s: None
    • 1
    • Tools and Replicator
    • 0.5

      Problem Statement/Rationale

      Passed: https://spruce.mongodb.com/task/mongo_tools_windows_qa_tests_7.0_3ce01a570d56f9943ebbabfb5078a88ea0ec6881_25_12_18_17_17_07/logs?execution=0

      Failed: https://spruce.mongodb.com/task/mongo_tools_windows_qa_tests_7.0_f0e99395519ed7ed25a4e871293cfd0f54c2818a_26_01_12_13_57_41?execution=0

      The difference seems to be that the earlier test was against 7.0.26 while the latter used 7.0.28.

      This seems to relate to this section of mongofiles_get.js:

          // This escaping is required because of a bug with argument quoting pre 8.1, fixed by SERVER-96103
    if (_isWindows()) {
      if (isAtLeastVersion(db.version(), "8.0.16")) {
        // no escaping needed
      } else if (!isAtLeastVersion(db.version(), "8.0.0") && isAtLeastVersion(db.version(), "7.0.27")) {
        // no escaping needed for 7.0.27 & later 7.0 releases
      } else {
        idAsJSON = '"' + idAsJSON.replace(/"/g, '\\"') + '"';
      }
    }

      The specific test error reflects a JSON-validity issue.

      Steps to Reproduce

      This has been broken on every waterfall run since.

      Expected Results

      This test should pass.

      Actual Results

      The test fails.

      Additional Notes

      This doesn’t affect production and need not impede the 100.14.1 release.

            Assignee:
            Unassigned
            Reporter:
            Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: