Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-3875

PowerShell - Improve PowerShellManager Resilience to Failure

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • PowerShell 2.0.3
    • powershell
    • None
    • Hide
      • The current behavior should be better documented in tests
      • In the face of a terminal failure inside the hosted PowerShell process, the PowerShellManager should create a new PowerShell process to execute the next PowerShell command
      • Such catastrophic errors should create actionable output for an end user (and should provide additional detail in the --debug stream)
      Show
      The current behavior should be better documented in tests In the face of a terminal failure inside the hosted PowerShell process, the PowerShellManager should create a new PowerShell process to execute the next PowerShell command Such catastrophic errors should create actionable output for an end user (and should provide additional detail in the --debug stream)
    • Modules
    • 2
    • Modules 2016-09-21

    Description

      Before being able to complete the pipe reimplementation in MODULES-3690, it became apparent that the current tests are insufficient to demonstrate how the current implementation behaves in the face of failures:

      • When the stdin, stdout or stderr streams are closed / broken
      • When user code terminates / crashes the underlying PowerShell process

      It also did not demonstrates how the manager behaves when given 64k+ of data from the Ruby side.

      Attachments

        Issue Links

          Activity

            People

              erick Erick Banks
              ethan Ethan Brown
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support