#18159 `pantsd` invalidation SIGTERM can cause spurious aborts Issue created by stuhood When a

pantsd

client attempts to connect to

pantsd

, it will determine whether the fingerprint of the process matches its options, and connect if so. If it doesn't match, it will SIGTERM the existing process, and connect to the next one. In some cases, this can cause errors similar to those reported in #18135. But trickily: this will only reproduce when a pipe is used for

pants

output. What I suspect is happening is that an open file handle to some previous run's pipe is having the

abort

rendered to it when the SIGKILL hits

pantsd

. Because another important aspect of the repro is that these errors do not cause the client to exit uncleanly: they proceed as if there was no abort (again, probably because it's a previous run's

pantsd

that was aborting). pantsbuild/pants