I've also encountered this, but only after hours of usage. I haven't investigated it yet. I've dug into the related code a bit, though:
We're using the high level fsnotify watchDir function from fileWatch, so I think that the issue is either there or the hinotify package it uses on linux. Here's the definition of removeWatch in hinotify:
I've noticed this before as well, but haven't been able to isolate what's going wrong. One correlation I noticed (that may or may not actually exist) is that it seems to happen after deleting directories with code in them that was being watched.
@mgsloan Another interesting thing I noticed is that running rm src/Data/Foo.hs in that project results in a stack running a rebuild .. and exiting successfully. Not sure if this is a bug. Looks like the object files are getting over-optimistically cached in .stack-work.
stack build --file-watchon in a local project intermittently results in the following message:
The solution is to restart stack. This seems to have appeared since upgrading to 1.0.4.
The text was updated successfully, but these errors were encountered: