This is blocked on a bunch of 1.3.0 issues, but primarily by #3941 and #3774: it should likely happen shortly into the 1.4.0.dev cycle, after #3941 is completed.
I think https://github.com/pantsbuild/pants/issues/5046 is the last blocker for this, afaict.
I think #5567 is now the last blocker here.
Coming back to this ticket, I think these are the blockers now:
I'm going to leave #6574 open for a bit (especially because I need to respond to some review comments), and before trying to merge it I will look at the open issues above and see if it might fix any of them (and add tests if so).
I would actually recommend adding #7080 as a blocker as well, as we do not have exception sink/logging testing for the pantsd case right now.
I am going to add #5220 and #7301 to the TODO to fix with #6579 if possible. As I just now noted on #7301, I believe that ticket may be very closely related to #5220 / the same cause, although the behavior is different.
After #7596 and some cleanup of very pressing bugs, the tasks for having a solid daemon seem to be:
DaemonExiter in DaemonPantsRunner and the main thread is also trying to exit through the PantsDaemon exiter, it's unclear which one should prevail. Some (but not all) context: #7597DaemonPantsRunner.create() should be moved, as described in #8002. This will make exception handling and the exit conditions so much easier.Feel free to add to this list.
The issues mentioned in https://github.com/pantsbuild/pants/issues/4438#issuecomment-509589275 should be resolved in #9722: a followup change will enable pantsd by default.
This is done for real in #9935. Thank you everyone!
Most helpful comment
This is done for real in #9935. Thank you everyone!