-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issue883/add check for different front end #933
Conversation
To Do:
|
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.
I was able to do a "beeflow core start" on a front end different than one that had beeflow running on it. I don't see a check for this in beeflow start command in core.py
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.
It looks like there is only a check for the commands beeflow core
status
and stop
There should also be checks for start
, restart
, and reset
.
It isn't needed for pull-deps
or info
though
@pagrubel I am not adding checks to |
That makes sense for |
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.
This works for reset and start now.
This PR adds a database to the client to keep track of the name of the front end where beeflow is started. Every time a
beeflow core *
command is submitted, we check if the current front end is the same as the one where beeflow was started from. If not, it returns a warning and exits.