use 4 spaces for e2e stack trace indentation

packages/server/__snapshots__/1_async_timeouts_spec.coffee.js

@@ -28,12 +28,12 @@ exports['e2e async timeouts / failing1'] = `
   1) async
        bar fails:
      CypressError: Timed out after \`100ms\`. The \`done()\` callback was never invoked!
-      [stack trace lines]
+    [stack trace lines]
 
   2) async
        fails async after cypress command:
      CypressError: Timed out after \`100ms\`. The \`done()\` callback was never invoked!
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/1_caught_uncaught_hook_errors_spec.coffee.js

@@ -44,21 +44,21 @@ exports['e2e caught and uncaught hooks errors failing1 1'] = `
      AssertionError: Timed out retrying: Expected to find element: \`.does-not-exist\`, but never found it.
 
 Because this error occurred during a \`before each\` hook we are skipping the remaining tests in the current suite: \`s1a\`
-      [stack trace lines]
+    [stack trace lines]
 
   2) s3a
        "before all" hook for "t8a":
      Error: s3a before hook failed
 
 Because this error occurred during a \`before all\` hook we are skipping the remaining tests in the current suite: \`s3a\`
-      [stack trace lines]
+    [stack trace lines]
 
   3) s4a
        "before all" hook for "t10a":
      Error: s4a before hook failed
 
 Because this error occurred during a \`before all\` hook we are skipping the remaining tests in the current suite: \`s4a\`
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -155,7 +155,7 @@ This behavior is configurable, and you can choose to turn this off by listening
 https://on.cypress.io/uncaught-exception-from-application
 
 Because this error occurred during a \`before each\` hook we are skipping the remaining tests in the current suite: \`s1b\`
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -239,7 +239,7 @@ This behavior is configurable, and you can choose to turn this off by listening
 https://on.cypress.io/uncaught-exception-from-application
 
 Because this error occurred during a \`before each\` hook we are skipping all of the remaining tests.
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -331,7 +331,7 @@ This behavior is configurable, and you can choose to turn this off by listening
 https://on.cypress.io/uncaught-exception-from-application
 
 Because this error occurred during a \`before each\` hook we are skipping the remaining tests in the current suite: \`s1\`
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/1_commands_outside_of_test_spec.coffee.js

@@ -91,7 +91,7 @@ When Cypress detects uncaught errors originating from your test code it will aut
 Cypress could not associate this error to any specific test.
 
 We dynamically generated a new test to display this failure.
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -181,7 +181,7 @@ Cypress could not associate this error to any specific test.
 We dynamically generated a new test to display this failure.
 
 https://on.cypress.io/cannot-execute-commands-outside-test
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/1_deprecated_spec.ts.js

@@ -310,7 +310,7 @@ exports['deprecated before:browser:launch args / displays errors thrown and abor
   Running:  app_spec.js                                                                     (1 of 2)
 Error thrown from plugins handler
 Error: Error thrown from plugins handler
-      [stack trace lines]
+    [stack trace lines]
 `
 
 exports['deprecated before:browser:launch args / displays promises rejected and aborts the run'] = `
@@ -332,5 +332,5 @@ exports['deprecated before:browser:launch args / displays promises rejected and
   Running:  app_spec.js                                                                     (1 of 2)
 Promise rejected from plugins handler
 Error: Promise rejected from plugins handler
-      [stack trace lines]
+    [stack trace lines]
 `

packages/server/__snapshots__/3_js_error_handling_spec.coffee.js

@@ -47,7 +47,7 @@ When Cypress detects uncaught errors originating from your application it will a
 This behavior is configurable, and you can choose to turn this off by listening to the \`uncaught:exception\` event.
 
 https://on.cypress.io/uncaught-exception-from-application
-      [stack trace lines]
+    [stack trace lines]
 
   2) s1
        without an afterEach hook
@@ -61,7 +61,7 @@ When Cypress detects uncaught errors originating from your application it will a
 This behavior is configurable, and you can choose to turn this off by listening to the \`uncaught:exception\` event.
 
 https://on.cypress.io/uncaught-exception-from-application
-      [stack trace lines]
+    [stack trace lines]
 
   3) s1
        with an afterEach hook
@@ -75,13 +75,13 @@ When Cypress detects uncaught errors originating from your application it will a
 This behavior is configurable, and you can choose to turn this off by listening to the \`uncaught:exception\` event.
 
 https://on.cypress.io/uncaught-exception-from-application
-      [stack trace lines]
+    [stack trace lines]
 
   4) s1
        with an afterEach hook
          t5:
      Error: baz
-      [stack trace lines]
+    [stack trace lines]
 
   5) s1
        cross origin script errors
@@ -105,7 +105,7 @@ This behavior is configurable, and you can choose to turn this off by listening
 https://on.cypress.io/uncaught-exception-from-application
 
 https://on.cypress.io/cross-origin-script-error
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/3_plugins_spec.js

@@ -288,7 +288,7 @@ exports['e2e plugins calls after:screenshot for cy.screenshot() and failure scre
 
   1) failure screenshot - rename:
      Error: test error
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -365,7 +365,7 @@ exports['e2e plugins fails when there is an async error inside an event handler
 The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file (\`/foo/bar/.projects/plugins-async-error/cypress/plugins/index.js\`)
 
  Error: Async error from plugins file
-      [stack trace lines]
+    [stack trace lines]
 
   (Results)
 
@@ -415,5 +415,5 @@ The following are valid events:
 - task
 - after:screenshot
 
-      [stack trace lines]
+    [stack trace lines]
 `

packages/server/__snapshots__/4_request_spec.coffee.js

@@ -125,11 +125,11 @@ Common situations why this would fail:
   - you have weird network configuration settings on your computer
 
 https://on.cypress.io/request
-      [stack trace lines]
+    [stack trace lines]
   
   From Node.js Internals:
     RequestError: Error: connect ECONNREFUSED 127.0.0.1:16795
-      [stack trace lines]
+    [stack trace lines]
     
 
 
@@ -248,7 +248,7 @@ Body: Service Unavailable
 
 
 https://on.cypress.io/request
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -375,7 +375,7 @@ Body: <!DOCTYPE html>
 </html>
 
 https://on.cypress.io/request
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/4_return_value_spec.coffee.js

@@ -38,7 +38,7 @@ For convenience, you can also simply omit any return value or return \`undefined
 In previous versions of Cypress we automatically detected this and forced the cy commands to be returned. To make things less magical and clearer, we are now throwing an error.
 
 https://on.cypress.io/returning-value-and-commands-in-test
-      [stack trace lines]
+    [stack trace lines]
 
   2) errors when invoking commands in custom command and returning different value:
      CypressError: Cypress detected that you invoked one or more cy commands in a custom command but returned a different value.
@@ -58,15 +58,15 @@ For convenience, you can also simply omit any return value or return \`undefined
 In previous versions of Cypress we automatically detected this and forced the cy commands to be returned. To make things less magical and clearer, we are now throwing an error.
 
 https://on.cypress.io/returning-value-and-commands-in-custom-command
-      [stack trace lines]
+    [stack trace lines]
 
   3) errors when not invoking commands, invoking done callback, and returning a promise:
      Error: Cypress detected that you returned a promise in a test, but also invoked a done callback. Return a promise -or- invoke a done callback, not both.
 
 Original mocha error:
 
 Error: Resolution method is overspecified. Specify a callback *or* return a Promise; not both.
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/5_cdp_spec.ts.js

@@ -39,7 +39,7 @@ The CDP port requested was 7777.
 Error details:
 
 Error: connect ECONNREFUSED 127.0.0.1:7777
-      [stack trace lines]
+    [stack trace lines]
 
 
 `
@@ -69,7 +69,7 @@ exports['e2e cdp / handles disconnections as expected'] = `
 There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.
 
 Error: connect ECONNREFUSED 127.0.0.1:7777
-      [stack trace lines]
+    [stack trace lines]
 
 
   (Results)

packages/server/__snapshots__/5_spec_isolation_spec.coffee.js

@@ -76,7 +76,7 @@ exports['e2e spec isolation fails'] = {
           ],
           "state": "failed",
           "body": "function () { }",
-          "stack": "Error: fail1\n\nBecause this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `beforeEach hooks`\n      [stack trace lines]",
+          "stack": "Error: fail1\n\nBecause this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `beforeEach hooks`\n    [stack trace lines]",
           "error": "fail1\n\nBecause this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `beforeEach hooks`",
           "timings": {
             "lifecycle": 100,
@@ -126,7 +126,7 @@ exports['e2e spec isolation fails'] = {
           ],
           "state": "failed",
           "body": "function () { }",
-          "stack": "Error: fail2\n\nBecause this error occurred during a `after each` hook we are skipping the remaining tests in the current suite: `afterEach hooks`\n      [stack trace lines]",
+          "stack": "Error: fail2\n\nBecause this error occurred during a `after each` hook we are skipping the remaining tests in the current suite: `afterEach hooks`\n    [stack trace lines]",
           "error": "fail2\n\nBecause this error occurred during a `after each` hook we are skipping the remaining tests in the current suite: `afterEach hooks`",
           "timings": {
             "lifecycle": 100,
@@ -196,7 +196,7 @@ exports['e2e spec isolation fails'] = {
           ],
           "state": "failed",
           "body": "function () { }",
-          "stack": "Error: fail3\n\nBecause this error occurred during a `after all` hook we are skipping the remaining tests in the current suite: `after hooks`\n      [stack trace lines]",
+          "stack": "Error: fail3\n\nBecause this error occurred during a `after all` hook we are skipping the remaining tests in the current suite: `after hooks`\n    [stack trace lines]",
           "error": "fail3\n\nBecause this error occurred during a `after all` hook we are skipping the remaining tests in the current suite: `after hooks`",
           "timings": {
             "lifecycle": 100,
@@ -299,7 +299,7 @@ exports['e2e spec isolation fails'] = {
           ],
           "state": "failed",
           "body": "function () {\n        return cy.wrap(true, {\n            timeout: 100\n        }).should(\"be.false\");\n    }",
-          "stack": "AssertionError: Timed out retrying: expected true to be false\n      [stack trace lines]",
+          "stack": "AssertionError: Timed out retrying: expected true to be false\n    [stack trace lines]",
           "error": "Timed out retrying: expected true to be false",
           "timings": {
             "lifecycle": 100,
@@ -328,7 +328,7 @@ exports['e2e spec isolation fails'] = {
           ],
           "state": "failed",
           "body": "function () {\n        throw new Error(\"fails2\");\n    }",
-          "stack": "Error: fails2\n      [stack trace lines]",
+          "stack": "Error: fails2\n    [stack trace lines]",
           "error": "fails2",
           "timings": {
             "lifecycle": 100,

packages/server/__snapshots__/6_task_spec.coffee.js

@@ -98,13 +98,13 @@ Fix this in your plugins file here:
 /foo/bar/.projects/e2e/cypress/plugins/index.js
 
 https://on.cypress.io/api/task
-      [stack trace lines]
+    [stack trace lines]
 
   2) includes stack trace in error:
      CypressError: \`cy.task('errors')\` failed with the following error:
 
 > Error: Error thrown in task handler
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/6_uncaught_spec_errors_spec.coffee.js

@@ -32,7 +32,7 @@ When Cypress detects uncaught errors originating from your test code it will aut
 Cypress could not associate this error to any specific test.
 
 We dynamically generated a new test to display this failure.
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -114,7 +114,7 @@ When Cypress detects uncaught errors originating from your test code it will aut
 Cypress could not associate this error to any specific test.
 
 We dynamically generated a new test to display this failure.
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -201,7 +201,7 @@ exports['e2e uncaught errors / failing3'] = `
   > foo is not defined
 
 When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
-      [stack trace lines]
+    [stack trace lines]
 
   2) foo
        fails with setTimeout and done:
@@ -210,7 +210,7 @@ When Cypress detects uncaught errors originating from your test code it will aut
   > foo is not defined
 
 When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
-      [stack trace lines]
+    [stack trace lines]
 
   3) foo
        fails with async app code error:
@@ -223,7 +223,7 @@ When Cypress detects uncaught errors originating from your application it will a
 This behavior is configurable, and you can choose to turn this off by listening to the \`uncaught:exception\` event.
 
 https://on.cypress.io/uncaught-exception-from-application
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -312,7 +312,7 @@ exports['e2e uncaught errors / failing4'] = `
 When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
 
 Because this error occurred during a \`before all\` hook we are skipping the remaining tests in the current suite: \`foo\`
-      [stack trace lines]
+    [stack trace lines]
 
 
 
@@ -395,22 +395,22 @@ exports['e2e uncaught errors / failing5'] = `
   1) foo
        baz fails:
      ReferenceError: foo is not defined
-      [stack trace lines]
+    [stack trace lines]
 
   2) foo
        bar fails:
      ReferenceError: foo is not defined
-      [stack trace lines]
+    [stack trace lines]
 
   3) foo
        quux fails:
      ReferenceError: foo is not defined
-      [stack trace lines]
+    [stack trace lines]
 
   4) foo
        quux2 fails:
      ReferenceError: foo is not defined
-      [stack trace lines]
+    [stack trace lines]
 
 
 

packages/server/__snapshots__/6_uncaught_support_file_spec.coffee.js

@@ -31,7 +31,7 @@ When Cypress detects uncaught errors originating from your test code it will aut
 Cypress could not associate this error to any specific test.
 
 We dynamically generated a new test to display this failure.
-      [stack trace lines]
+    [stack trace lines]