-
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
Visualize dag #903
Visualize dag #903
Conversation
…er. Can definitely see a lot of reworking in terms of the interfaces & will have to go to drawing board for that
…id in calls to gdb_driver
…/ stop / kill gdb atm)
Accidental save from vim
… start / stops on beeflow core stop
… into Multiple-Workflows-One-Database
… central code. Load containers in foreground, will change to background later
Restructure dep_manager and separate container, redis, and neo4j from…
…t unit tests to match code
Currently in wf_utils I'm triggering exporting of the dag within the --no-start flag. I'm planning on making a new flag, I just wanted to see how things worked first. |
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.
The changes made to bee_client.py and wf_utils.py are causing the NOT_RESPONDING state to appear -- I think. But this is my first attempt at having the "beeflow dag" command.
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.
Do the steps actually complete and then show NOT_RESPONDING ?
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.
Yes
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.
Just to note, I'm not planning on keeping this here. I just wanted to put my work somewhere while I'm figuring things out.
Switched to PR Export dag #909 |
This branch is one that comes off of Kabir's Multiple-Workflows-One-Database branch. The purpose of it is to enable users to look at the dag without having to go to the web browser. I want to save the dag in a common format like .gml or dot so then users can put that file into a tool like graphviz.
Before I made the pull request I did
git merge develop
because the Multiple-Workflows-One-Database branch didn't have changes from develop.