New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interrupting nanoc compile
corrupts change tracking
#1641
Comments
Can you check whether this is fixed by #1644? I cannot reproduce this issue myself, and Nanoc is supposed to handle interrupted compilation correctly (mark only already-compiled files as non-outdated). |
Sorry, this does not resolve it. I added Thinking it might be something about my specific project, I have I tried to reproduce it on another project and the problem occurred there too. Most other nanoc repos I have are small enough that it's tricky to interrupt compilation half way through, but I managed to reliably reproduce the problem by adding a filter to the compilation step with |
@Fjan Is there a chance you could share the project with me so I could take a look? |
It's a private repo, a company internal thing, but I can email you a zip file if you want? |
This is fixed in the just-released Nanoc 4.12.18. |
Steps to reproduce
nanoc compile
and interrupt it shortly afterwards with ctrl-Cnanoc compile
once more in order to finish the compilationExpected behavior
The site should be compiled in it's entirety.
Actual behavior
The compilation is not resumed, only the files before the interrupt have been compiled
Details
I can think of several acceptable ways to behave upon interruption:
I would argue the current behaviour where it does not compile the remaining outdated files after an interrupt is dangerous, because it may go unnoticed, causing someone to release/upload a site that's not fully compiled.
The text was updated successfully, but these errors were encountered: