-
Notifications
You must be signed in to change notification settings - Fork 1
Feat: Add Procedures HLI #701
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
Conversation
a39f75a to
eb7e19d
Compare
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
b276fcc to
97b79a3
Compare
- helper on the client to call procedures - procedure to run a loaded macro function - status object for procedures executed this way - tests
9cd838a to
7ce805f
Compare
7ba475b to
0413bfa
Compare
bf32bc2 to
1b9afa2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! A couple of minor comments. For me it worked good, although I was unable to start a procedure with "run_scan" through the CLI. Maybe we can check that briefly together tomorrow.
1b9afa2 to
ef116b4
Compare
and fix a few small errors
ef116b4 to
78f5348
Compare
|
@wakonig that's right, I already started drafting it, I just didn't want to pile more stuff on this PR |
closes #681
To test procedures locally you can start the BEC server with:
bec-server start --use-in-process-proc-worker, this will avoid the use of podman.Introduces a high level interface in the BEC client to manage procedures, with a convenience function to run a loaded macro
Also starts the procedure runner as part of the scan server
You can operate it from
bec.proc, e.g.:and get a list of available procedures like: