Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

```[omerta pants (kwlzn/repl_echo)]$ PANTS_ENABLE_PANTSD=True ./pants -ldebug help
DEBUG] Selected watchman binary bootstrapped to: /Users/kwilson/.cache/pants/bin/watchman/mac/10.12/4.5.0/watchman
DEBUG] Executing: git --git-dir=/Users/kwilson/dev/pants/.git --work-tree=/Users/kwilson/dev/pants rev-parse --abbrev-ref HEAD
DEBUG] Detected git repository at /Users/kwilson/dev/pants on branch kwlzn/repl_echo
DEBUG] Target alias resources has already been registered. Overwriting!
DEBUG] ProjectTree ignore_patterns: ['.*/', '/dist/', '/build-support/*.venv/']
DEBUG] loading native engine python module from: /var/folders/bb/msvj_4_s741g93nzgrj19twc0000gn/T/tmpsADAzL
DEBUG] Selected watchman binary bootstrapped to: /Users/kwilson/.cache/pants/bin/watchman/mac/10.12/4.5.0/watchman
DEBUG] watchman is running, pid=27350 socket=/Users/kwilson/dev/pants/.pids/watchman/watchman.sock
DEBUG] acquiring lock: &lt;pants.process.lock.OwnerPrintingInterProcessFileLock object at 0x107a5a650&gt;
DEBUG] pantsd: is_alive=False new_fingerprint=6877aa1c62cc3e07fdac39cd47ee99e9b3f0b6fd current_fingerprint=1348d310e6b64a785a999e95c594096978ec64e5
DEBUG] purging metadata directory: /Users/kwilson/dev/pants/.pids/pantsd
DEBUG] launching pantsd```

sorry, i'm just talking about the FSEventsService probably.

so that relates to the event.wait() we do on teh first run

the "receiving initial event" bit is the thing that acquires the lock, afaik

anywho. i'll just toggle over to the pex change for a bit and let you look at this.

will land <https://github.com/pantsbuild/pants/pull/5192> when it goes green

<@U054MQUPL>: so, next off the top of <https://github.com/pantsbuild/pants/milestone/11> ... should the double echo thing be part of this milestone, or just part of `1.4.x` ?

ok. do we think it blocks the next hotfix we cut?

ideally theres no difference between daemon vs daemonless repl

i mean, as you said: "ideally"... but on the other hand, it would be good to discover more substantive crashers/deadlocks/etc

the pants server stuff seems maybe higher priority...

it's also possible that the documentation could be bumped out of the beta and into 1.4.x

my take is that #5194 and #5140 are blockers for the next internal release

works for me, there’s also the DPB Daniel filed re: initial clean-all costs

or may end up alleviating a bit of it in #5194

I wonder if it would ever make sense for us to ship a fs alongside pants in lieu of watchman/inotify