-
Notifications
You must be signed in to change notification settings - Fork 218
Proposed way to add breakpoints to easybuild #5036
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
base: develop
Are you sure you want to change the base?
Conversation
|
Is there any benefit to having the option to jump into a python prompt? (Would that already be possible somehow with |
|
You mean something like adding a My main usecase for this is to test stuff in a build environment at the start/end of a step when you don't have a |
|
Essentially yes. My thinking being that if you drop into a bash shell, you still can't understand why EB is doing what it's doing, and some way to interrogate the internal structures/variables might be useful. Your usecase makes perfect sense, I was just wondering if getting at the internal state might be useful as well? |
73748af to
820a464
Compare
5739b7d to
d80b9de
Compare
|
@hattom Added a way to gain a Let's see what others think about this as well |
Feature proposed during the 2025-10-22 EB confcall
Adds a new
--breakpointsoption that takes a comma-separated list of breakpoint names.The names should be the same as those for available hooks (with or without the trailing
_hooksuffix).EB will drop you into an interactive shell with the same environment (before the corresponding hook would be ran)
TODO
Maybe
How does this look