Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runspaces need to provide more debugging output #2843

Open
CodingWonders opened this issue Sep 28, 2024 · 1 comment
Open

Runspaces need to provide more debugging output #2843

CodingWonders opened this issue Sep 28, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@CodingWonders
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Yes. Trying to diagnose a problem with the code that is run with runspaces on MicroWin (#2731) is next to impossible because debuggers can't get to the actual code that is being run

Describe the solution you'd like
Provide debugging for runspaces. Something that can be turned on or off via a flag

Describe alternatives you've considered
None

Additional context
None

@CodingWonders CodingWonders added the enhancement New feature or request label Sep 28, 2024
@CodingWonders CodingWonders changed the title Runspaces need to provide enough debugging output Runspaces need to provide enough debugging output and Write-Error problems Sep 28, 2024
@CodingWonders CodingWonders changed the title Runspaces need to provide enough debugging output and Write-Error problems Runspaces need to provide enough debugging output Sep 28, 2024
@CodingWonders CodingWonders changed the title Runspaces need to provide enough debugging output Runspaces need to provide more debugging output Sep 28, 2024
@MyDrift-user
Copy link
Contributor

in addition, write-error just does nothing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants