Closed lucpeterson closed 2 months ago
So that I can keep track of them all, I'm adding on to this thread with a few additional bugs with the status command that I've encountered:
For detailed status, I need to add in the export MANPAGER="less -r"
call behind the scenes so users don't have to do this.
@lucpeterson I'm looking into the bug you mentioned now but I'm unable to reproduce. When I run a study with merlin v1.11.1 and then try to check the status with merlin v1.12.0 it just shows empty progress bars:
Which study were you running that caused this? Maybe there's a certain case where this happens but won't otherwise
This was not actually a problem with status but rather a server timeout delay that made it look like it hangs
Bug Report
Describe the bug It looks like if you run the new “status” command on a workflow that was run with old merlin, it will just hang as it searches for the status files.
To Reproduce Steps to reproduce the behavior:
Expected behavior Some kind of warning, a direction to use the old command, and a graceful exit