You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This shouldn't occur by the user, we only added the -B flag to beeflow core start for CI purposes. However, someone might start beeflow from a compute node anyway. In my case the wf_manager would not start and then I couldn't do a beeflow core stop. We should make it easier to recover from that. I was able to do so by deleting client.db, but that doesn't seem like the best route.
I guess this is not a priority, just wanted to put it on the radar screen.
The text was updated successfully, but these errors were encountered:
This shouldn't occur by the user, we only added the -B flag to
beeflow core start
for CI purposes. However, someone might start beeflow from a compute node anyway. In my case the wf_manager would not start and then I couldn't do abeeflow core stop
. We should make it easier to recover from that. I was able to do so by deleting client.db, but that doesn't seem like the best route.I guess this is not a priority, just wanted to put it on the radar screen.
The text was updated successfully, but these errors were encountered: