Title: Inconsistent Start-Transcript behavior with respect to the error and information streams · Issue #4645 · PowerShell/PowerShell · GitHub
Open Graph Title: Inconsistent Start-Transcript behavior with respect to the error and information streams · Issue #4645 · PowerShell/PowerShell
X Title: Inconsistent Start-Transcript behavior with respect to the error and information streams · Issue #4645 · PowerShell/PowerShell
Description: I'm making the following assumptions about how Start-Transcript is designed to work (can't tell from the documentation): Whatever streams are neither captured nor redirected are transcribed, and preference variables with respect to which...
Open Graph Description: I'm making the following assumptions about how Start-Transcript is designed to work (can't tell from the documentation): Whatever streams are neither captured nor redirected are transcribed, and pr...
X Description: I'm making the following assumptions about how Start-Transcript is designed to work (can't tell from the documentation): Whatever streams are neither captured nor redirected are transcribed...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/4645
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Inconsistent Start-Transcript behavior with respect to the error and information streams","articleBody":"I'm making the following assumptions about how `Start-Transcript` is designed to work (can't tell from the documentation):\r\n\r\n* Whatever streams are neither captured nor redirected are transcribed, and preference variables with respect to which `Write-*` cmdlets should actually produce output are honored; another way of putting it: Whatever output displays in the console, across all streams, is also what should get transcribed.\r\n\r\nCurrently, `Start-Transcript` doesn't always work that way:\r\n\r\n* Even with `*>$null` applied to a script that uses `Start-Transcript`, which should keep _all_ streams out of the transcript, _errors_ (stream 2) and `Write-Host` output (stream 6) are still transcribed.\r\n\r\n * You can _partially_ keep error output out of the transcript If you use `$ErrorActionPreference = 'SilentlyContinue'`: outside of a transcript that would silence _all_ errors (non-terminating, statement-terminating, script-terminating - albeit the latter two against documented behavior), but in a transcript _cmdlet-triggered_ statement-terminating errors are unexpectedly still transcribed.\r\n\r\n * Errors that do get transcribed are transcribed *twice* by default.\r\n\r\n * _Cmdlet-triggered_ statement-terminating errors are preceded by an _extra line_ repeating the error message, with a prefix such as `>>TerminatingError(\u003ccommand>): \u003cmessage>` \r\nIt is this line that shows in the transcript even with `$ErrorActionPreference = 'SilentlyContinue'` in effect.\r\n\r\n * Unlike outside of a transcript, with `$ErrorActionPreference` at its default, `$Continue`:\r\n * a _cmdlet-triggered_ statement-terminating error acts like a _script_-terminating one.\r\n * a script-terminating error prints neither to the console nor records the error in the transcript.\r\n * the transcript is _aborted_ in both cases, however.\r\n\r\n* ~~Even though `Write-Information` output (stream 6) is by default _not_ printed to the console `$InformationAction` is `'SilentlyContinue'` by default), it is still transcribed.~~ [_Update_: This appears to have been fixed, but I don't know where and when (the problem persists in _Windows PowerShell_)]\r\n\r\n\r\n\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\nCreate script `t.ps1` with the following content:\r\n\r\n```powershell\r\n$null = Start-Transcript t.log\r\n\r\nwrite-warning 'warn'\r\nwrite-verbose 'verbose'\r\n\r\nwrite-information 'info'\r\nwrite-host 'host'\r\n\r\nwrite-output 'data'\r\n\r\n# Generate a non-terminating error\r\nWrite-Error 'error'\r\n\r\n# Generate an expression-based statement-terminating error.\r\n1/0\r\n\r\n# Generate a cmdlet-based statement-terminating error.\r\nGet-Item -NoSuchParam\r\n\r\n$null = Stop-Transcript\r\n```\r\n\r\nThen run the following commands, one after the other:\r\n\r\nA)\r\n```powershell\r\n./t.ps1\r\n```\r\n\r\nB)\r\n```powershell\r\n./t.ps1 *>$null\r\n```\r\n\r\nC) \r\n```powershell\r\n& { $ErrorActionPreference = 'SilentlyContinue'; ./t.ps1 }\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\nInspect output file `t.log`:\r\n\r\nA)\r\nColoring aside, whatever printed to the console should appear in the transcript (sandwiched between a header and a footer).\r\n\r\nB)\r\nExcept for the header and footer, the transcript should be empty (all streams were suppressed).\r\n\r\nC)\r\nNo errors of any kind should be transcribed.\r\n\r\nActual behavior\r\n---------------\r\n\r\nA)\r\n\r\n* ~~`INFO: info` shows in the transcript, even though it doesn't show in the console (with `$InformationPreference` at its default value, `SilentlyContinue`).\r\nAs an aside: Non-suppressed `Write-Information` output in the _console_ has _no_ `INFO: ` prefix , but does in the _transcript_ (whereas `Write-Warning`, `Write-Verbose` and `Write-Debug` print a prefix in _both_ scenarios).~~\r\n\r\n[_Update_: This appears to have been fixed, but I don't know where and when (the problem persists in _Windows PowerShell_)]\r\n\r\n* All errors show _twice_ in the transcript.\r\n * The _first_ instance of the cmdlet-triggered statement-terminating error is preceded by an extra line duplicating the regular error representation: \r\n`>> TerminatingError(Get-Item): \"A parameter cannot be found that matches parameter name 'NoSuchParam'.\"`\r\n\r\nB)\r\n\r\n* `host` (`Write-Host` output) still shows in the transcript.\r\n\r\n* All errors still show in the transcript (now only _once_).\r\n\r\nC)\r\n\r\nWhile the non-terminating error and the expression-triggered error were successfully suppressed, the _cmdlet-triggered_ _terminating_ error still shows in the transcript, but only by the extra line: \r\n`PS>TerminatingError(Get-Item): \"A parameter cannot be found that matches parameter name 'NoSuchParam'.\"`\r\n\r\nEnvironment data\r\n----------------\r\n\r\n\u003c!-- provide the output of $PSVersionTable -->\r\n\r\n```powershell\r\nPowerShell Core v6.0.0-beta.5 on macOS 10.12.6\r\nPowerShell Core v6.0.0-beta.5 on Ubuntu 16.04.3 LTS\r\nPowerShell Core v6.0.0-beta.5 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\nWindows PowerShell v5.1.15063.483 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2017-08-22T22:05:50Z","url":"https://github.com/PowerShell/PowerShell/issues/4645"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:5c9baccb-598f-bcf6-aba6-9d5baef8d3c9 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C8FA:365F07:EEB06:13DA54:6AFD0DD6 |
| html-safe-nonce | 57e07cbdcf761608b605180ce3266958296e16aeffc65eda83859270d86e2128 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDOEZBOjM2NUYwNzpFRUIwNjoxM0RBNTQ6NkFGRDBERDYiLCJ2aXNpdG9yX2lkIjoiNTkyMjM0MzM3Mjc1NTYzNTY3MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 7659b605b12a1b74c2977186283f866b2399a9638866b68c8bf5cd06c7d20866 |
| hovercard-subject-tag | issue:252103310 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/4645/issue_layout |
| twitter:image | https://opengraph.githubassets.com/57a10585e47f06bcd08654c64b577af2a2e527997b69df63fbddba6f29c39cc7/PowerShell/PowerShell/issues/4645 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/57a10585e47f06bcd08654c64b577af2a2e527997b69df63fbddba6f29c39cc7/PowerShell/PowerShell/issues/4645 |
| og:image:alt | I'm making the following assumptions about how Start-Transcript is designed to work (can't tell from the documentation): Whatever streams are neither captured nor redirected are transcribed, and pr... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | mklement0 |
| hostname | github.com |
| expected-hostname | github.com |
| None | b29de2abb97b6307b16270785efeb58b51a117d5a9b659acf00b77aa00e7043b |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c9e619def6d670dc18a45d3b02cea938c1c7e47 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width