dmypy status reports as "stuck" when it's busy checking files
#18008
Labels
Comments
|
I find the following code: # mypy/dmypy/client.py
@action(status_parser)
def do_status(args: argparse.Namespace) -> None:
...
response = request(
args.status_file, "status", fswatcher_dump_file=args.fswatcher_dump_file, timeout=5
)
if args.verbose or "error" in response:
show_stats(response)
if "error" in response:
fail(f"Daemon is stuck; consider {sys.argv[0]} kill")
...It seems the current implementation sets a 5-second timeout for IPC communication to |
kcornw
added a commit
to kcornw/mypy
that referenced
this issue
Dec 23, 2024
Update the status message to clarify that the daemon may be busy and not necessarily stuck. The new message provides better guidance to users without prematurely suggesting killing the daemon. Fixes python#18008
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 statuson it during this time, I seeI 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 runwill 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 acheck/start/stopflow. Is there a way to get a better status than this?The text was updated successfully, but these errors were encountered: