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

Foreach -Parallel Breakpoints? #1689

Open
JustinGrote opened this issue Jan 31, 2022 · 0 comments
Open

Foreach -Parallel Breakpoints? #1689

JustinGrote opened this issue Jan 31, 2022 · 0 comments
Labels

Comments

@JustinGrote
Copy link
Collaborator

Just thought I'd throw this discussion point out there.

If we know by the AST that someone is doing foreach -parallel, we are going to know the behavior. Can we hook into those created runspaces and drop breakpoints there, and then maybe monitor for them to go into InBreakpoint state and trigger the debugger there?

The net effect would be that users could put breakpoints in a Foreach -Parallel loop and expect it to break there for troubleshooting parallel runs, rather than the current procedure of removing -Parallel and any $USING references in order to debug.

Probably not feasible, lots of issues:

  1. How do we pause the other runspaces at the same time
  2. Have to fetch all the state and ensure it works the same thru all the existing tests
  3. etc.
@ghost ghost added the Needs: Triage Maintainer attention needed! label Jan 31, 2022
@StevenBucher98 StevenBucher98 added Issue-Discussion Let's talk about it. Area-Debugging and removed Needs: Triage Maintainer attention needed! labels Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants