You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If puppet-lint experiences a catastrophic error it polutes STDOUT with Whoops! It looks like puppet-lint has encountered an error that it doesn't\nknow how to handle. Please open an issue at https: "//github.com/rodjek/puppet-lint\nand paste the foll… which causes the LSP STDIO transport to fail in the client.
All STDIO output from puppet-lint should be suppressed
The text was updated successfully, but these errors were encountered:
Previously some libraries, like puppet-lint, would use $stdout to output
information to STDOUT instead of using a logging mechanism which could be
monkey patched or configured to not output. This commit updates the STDIO
transport to reassign the global $stdout variable to a null stream.
Previously some libraries, like puppet-lint, would use $stdout to output
information to STDOUT instead of using a logging mechanism which could be
monkey patched or configured to not output. This commit updates the STDIO
transport to reassign the global $stdout variable to a null stream.
Initially raised in puppetlabs/puppet-vscode#436
If puppet-lint experiences a catastrophic error it polutes STDOUT with
Whoops! It looks like puppet-lint has encountered an error that it doesn't\nknow how to handle. Please open an issue at https: "//github.com/rodjek/puppet-lint\nand paste the foll…
which causes the LSP STDIO transport to fail in the client.All STDIO output from puppet-lint should be suppressed
The text was updated successfully, but these errors were encountered: