I have left my computer running for a few hours and when I got back, I could no longer run pants, because it said "too many open files". I killed the pantsd process, and then it started working again. I guess that file descriptors are leaking somewhere. Is this a known issue?

It is not known to me at least. Which pants version?

2,14.0rc1

Oh, have you followed this advice about ulimit? https://www.pantsbuild.org/docs/troubleshooting#too-many-open-files-error

Yes, I have the limit set to a high value.

Is your repo particularly large, with many changed files or something?

No, it's not large. count-loc reports 123 files. I have been working on it all day, and there were no issues. Only when left unattended for some hours. I don't know if it's related, could be on top of the other hours I was working, of course. Maybe it's worth making a mental note and if more people mention it, try to investigate.

thanks for the report! if you experience this again, running

lsof -p $pantsd_pid

would be helpful to determine what is open, and then filing an issue.

you can find the pid by using

ps aux | grep pants

pantsd

in particular, yea