https://pantsbuild.org/ logo
Join Slack
Powered by
When running Pants commands I'm seeing `Filesystem...
# general
b
When running Pants commands I'm seeing `Filesystem changed during run: retrying 
Lint
in 500ms...` happen seemingly sporadically. Is there any way to dive into which file(s) changed? Admittedly my setup is weird as we transition to Pants. I'm running Pants in a subprocess from Python being run as a 
bazel run myscript.py
command. So there's probably shenanigans happening, but understanding what changed would help me narrow the shenanigan-er
According to the code, I don't see any 
debug
calls. Additionally, I'd prefer not to turn off 
watch_filesystem
because `pantsd`'s caching is good 🙂
c
you should see stuff like this in your 
.pants.d/pants.log
Copy code
17:13:38.70 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {"src/python/pants", "src/python/pants/version.py"}
that can help guide you what to add to pants/git ignore 😉
b
Weird.
Copy code
10:15:07.37 [INFO] notify invalidation: cleared 0 and dirtied 0 nodes for: {"mcd/techlabs/modname/data/products.db", "mcd/techlabs/modname/data"}
c
so, something is touching that 
.db
file… ?
b
I don't expect anything to be
Certainly 
git
doesn't ever show it as dirty
c
ok, weird 🙂
well, it doesn’t have to change contents..
b
Both 
accessed
and 
modified
show: 
Tue 11 Jan 2022 03∶45∶56 PM CST
c
hah. well, inotify seems to think it changed.. no idea why, open up dtrace for syscalls? 😛
🥴 1
b
Maybe I should make this a 
pex_binary
and run it using Pants. Then at least it is Pants running Pants 🧙
c
twin pants, or “pants in pants”
b
Must be cold out 🤔
c
pinp..
b
Ok running pants directly also has this symptom, so Bazel is a red herring
👍 1
Although Bazel does open a lot of symlinks and has a daemon, so could still be a problem. I'll just ignore the file for now
I might need some help later debugging the inotify notification. I'm a relatively newbiush Unix user
5 Views
Open in Slack
PreviousNext
Powered by