https://pantsbuild.org/ logo
Join Slack
Powered by
Hey all, thanks for your great work on pants. I'm ...
# development
h
Hey all, thanks for your great work on pants. I'm facing a 
MaxFilesWatch
error when running goals, and I don't have control over that number on this system (8192). However, why are there so many watches to begin with? There are <1000 source files in this repo. #21451 Allow --no-watch-filesystem with --pantsd
h
Hmm, is your use case similar to the one in that ticket, where you don’t actually need file watching at all? Or is this an interactive session where it’s important to have file watching, but you’re wondering why the number of watches is so high?
Also, what happens when you kill the 
pantsd
process? Does that give you more breathing room? In other words, does this problem accumulate over time, or does it happen immediately?
Also, what platform is this on? Keep in mind that 8192 is a very low number in general for practical file watching.
h
I would say it's both. • I need pantsd to run even in an environment with low watch limits. • And I wonder why the number is high in the first place (~1000 source files)
This is containerized Linux. I can't control the watch limit.
The problem seems to appear on a freshly created container. We start by running 
pantsd --version
, and it sometimes crashes there already.
h
Hmm, and is your pants_ignore appropriately set? I wonder if there are files you don’t care about that are nonetheless being watched
h
I assume it's something like that.
For pants ignore, I'm relying on gitignore.
I came across 
inotify-info
, so I'm trying
Copy code
pants --version && inotify-info $(pgrep -f pantsd)
But haven't been able to reproduce the problem reliably (it's a 1 in a 100 situation)
9 Views
Open in Slack
PreviousNext
Powered by