Error Handling for Commands #63

Activity

1. Jason Helmick (theJasonHelmick)

   added

   Issue-Triagedissue was read and triagedissue was read and triaged

   on Mar 9, 2021
2. theJasonHelmick commented on Mar 9, 2021

   

   Jason Helmick (theJasonHelmick)

   on Mar 9, 2021

   Collaborator

   More actions

   You raise an excellent point and we should consider error handling. I haven't added this to a milestone yet, but let's open the discussion here and get everyones feedback regarding concerns and implementation ideas.
3. ethanbergstrom commented on Mar 27, 2021

   

   Ethan Bergstrom (ethanbergstrom)

   on Mar 27, 2021

   Last edited by ethanbergstrom

   More actions

   +1 on error handling. Chocolatey packages, for example, allow the package owner to specify a list of successful exit codes, and everything else gets treated as an error. Without a programmatic way to catch and handle error signals returned by the native command, we're left trying to guess how to parse the native command output for "uniquely error-like" text and throw an exception in the handler.

   👍React with 👍2Reacted by Thomas Nieto and Doug Bailey
4. kstrauss commented on Jul 28, 2021

   

   Karl Strauss (kstrauss)

   on Jul 28, 2021

   Last edited by kstrauss

   More actions

   A few things that occur to me:

   1. need to be able to specify a list of "good" return codes or a list of bad ones. Some applications have a return code say that means finished with warnings. Not sure how to represent other than perhaps a flag of TreatWarningsLikeErrors
   2. Need to be able to ignore the return code and instead delegate to a function/script that deduces it from output (because the return code is always 0). Ideally, I would like a set of established ones (i.e. any output to stderr is an error, regex for pattern)
   3. potentially add a list of handling strategies (throw exception, have a retry, retry with backoff, timeout, etc. like exists in Polly ) that should be added as parameters/switches on the generated wrapper. Should still support standard parameters like ErrorVariable
5. PowerShell

   locked and limited conversation to collaborators on Nov 16, 2021
6. James Truher (JamesWTruher)

   closed this as completedon Nov 16, 2021