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
It's pretty easy to press Ctrl-C while the RemotePantsRunner client is waiting for the pantsd pid, within a time window which causes an immediate deadlock, requiring killing pantsd in another terminal.
I went over this with @blorente yesterday in the context of #6574, but I now believe it will probably have to be addressed as part of #6579.
The text was updated successfully, but these errors were encountered:
I believe this may be a duplicate of #5220, except that that ticket describes pants running to completion, while this ticket describes a deadlock in which the terminal is frozen and pants also refuses to run. I suspect these are closely related events, and I intend to fix both in #6579.
It's pretty easy to press Ctrl-C while the
RemotePantsRunner
client is waiting for the pantsd pid, within a time window which causes an immediate deadlock, requiring killing pantsd in another terminal.I went over this with @blorente yesterday in the context of #6574, but I now believe it will probably have to be addressed as part of #6579.
The text was updated successfully, but these errors were encountered: