Skip to content
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

output.diff not always generated; possibly a threading issue #225

Closed
tbm opened this issue Feb 16, 2013 · 2 comments
Closed

output.diff not always generated; possibly a threading issue #225

tbm opened this issue Feb 16, 2013 · 2 comments

Comments

@tbm
Copy link

tbm commented Feb 16, 2013

output.diff is sometimes not generated, even though the output has changed:

$ md5sum output/index.html
7c616b023c5f593d57e5b6f5eec1ecbe  output/index.html
$ nanoc compile
Loading site data… done
Compiling site…
      update  [0.02s]  output/index.html

Site compiled in 0.04s.
$ md5sum output/index.html
dfddc976758c15d6c3e3933636aceed3  output/index.html
$ ll output.diff
ls: cannot access output.diff: No such file or directory

I believe this may be a threading issue... when I started adding debug statements using 'warn' in generate_diff_for, the information wasn't always printed.

@tbm
Copy link
Author

tbm commented Apr 5, 2013

to reproduce, git clone https://github.com/tbm/homepage
compile
then edit content/index.md and remove the line hide_date: true
compile again and usually there's no output.diff

I added warn statements to generate_diff_for and this info is not always printed·

@denisdefreyne
Copy link
Member

This is fixed in #301.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants