pulp server misses recompilations

[Rufflewind]

I'm using pulp server for development and every so often I would run into situations where it fails to rebuild all the changes I made, leading to spurious errors.

Emacs creates lockfiles as soon as I start editing a file – dummy (broken) symbolic links prefixed with .#. They always trigger spurious rebuilds with pulp. As a result, it's very common to end up in a situation where I save a file while pulp is still building (does pulp have a way to exclude files by pattern?).

Here's a somewhat hacky way to reproduce it. Make an empty project with Main and Foo modules. Add import Foo (foo) to Main and add foo = 0 to Foo. Then create a "bad" version of Foo that doesn't define foo at all. Now, build the project and let it finish.

Then run this script:

touch src/dummy &&                # trigger rebuild
sleep 0.1 &&                      # delay
cp /tmp/Foo_bad.purs src/Foo.purs # change file

Expected behavior: compilation should fail.
What actually happens: compilation succeeds!?

The time might have to be adjusted – basically there's a short goldilocks window during which pulp would miss the change to the file. For a small project, the window is short but still large enough to that you can trigger it manually. For a larger project, the window is pretty hard to miss.

[hdgarrood]

Argh, that's annoying. Thanks for the report. I doubt I'll get around to looking at this any time soon unfortunately.