dmypy status reports as "stuck" when it's busy checking files · Issue #18008 · python/mypy (original) (raw)

I wanna use dmypy to help with checking my large company codebase. I've noticed on first check, or when checking a large number of files it will take a few dozen seconds to return (expected for my large repo). However, when I do dmypy status on it during this time, I see

error                   :  timed out
Daemon is stuck; consider /usr/scratch/pthompson/junk/ops3venv11/bin/dmypy kill

I don't think this is correct. It's not "stuck", it's just busy and I'm fairly confident it will return an answer eventually. But I think this means dmypy run will attempt to start another daemon during this time (if I spam it with a for loop I can get into a funky state); and it might be harder to build tooling around a check/start/stop flow. Is there a way to get a better status than this?