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

add debug_remote_on_single_rank #496

Conversation

matthiasdiener
Copy link
Contributor

@matthiasdiener matthiasdiener commented Dec 16, 2021

Needs #486.

@inducer
Copy link
Owner

inducer commented Dec 28, 2021

Thanks for making this. I think this is a bit too specific to mpi4py to be of broad use, especially with as little documentation as it currently has.

@matthiasdiener
Copy link
Contributor Author

Thanks for making this. I think this is a bit too specific to mpi4py to be of broad use,

Do you have a suggestion on how to improve it?

especially with as little documentation as it currently has.

Do you mean the documentation specifically for debug_remote_on_single_rank or for the remote debugging feature in general?

@inducer inducer force-pushed the remote-fixes branch 2 times, most recently from 4fe6f7c to 5f7e129 Compare December 28, 2021 17:36
@inducer inducer deleted the branch inducer:remote-fixes December 28, 2021 17:38
@inducer inducer closed this Dec 28, 2021
@inducer
Copy link
Owner

inducer commented Dec 28, 2021

Sorry, I did not mean to close this. I think it got auto-closed because the base branch went away.

Do you mean the documentation specifically for debug_remote_on_single_rank or for the remote debugging feature in general?

I guess I could be talked into adding something like this, as long as it's

  • included in the docs, and
  • it has sensible semantics and is well-explained in terms of what it does. (what happens to the other ranks? they spin. what does the rank argument do? allow passing a communicator)

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

Successfully merging this pull request may close these issues.

None yet

2 participants