Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8926

Shell displays "JavaScript execution failed: " before all JavaScript errors, adds "L" before line number

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.4.0-rc2
    • Fix Version/s: 2.4.6, 2.5.1
    • Component/s: JavaScript, Shell
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL

      Description

      For version 2.4.0-rc0, we had mimicked the error reporting from version 2.2.

      MongoDB shell version: 2.2.4-pre-
      > var v = foo.bar.baz;
      Sat Mar 09 14:16:35 ReferenceError: foo is not defined (shell):1

      MongoDB shell version: 2.4.0-rc0
      > interpreterVersion()
      V8 3.12.19
      > var v = foo.bar.baz;
      Sat Mar 09 14:51:40.597 ReferenceError: foo is not defined (shell):1

      In version 2.4.0-rc2, we are getting extra text that seems unnecessary:

      MongoDB shell version: 2.4.0-rc2
      > interpreterVersion()
      V8 3.12.19
      > var v = foo.bar.baz;
      Sat Mar 09 15:02:25.723 JavaScript execution failed: ReferenceError: foo is not defined

      We also lost the "(shell):1" text, but that might be consider a "feature".

      It would be nice to get rid of the "JavaScript execution failed: " text.

      Also, commit https://github.com/mongodb/mongo/commit/f11d2b67e2f185a0934d76cca21361b0679e5301 added an "L" before the line number, which does not match prior error logging.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tad Tad Marshall
                Reporter:
                tad Tad Marshall
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: