Unclear cache behavior

[beverlycodes]

I've got a plugin that handles Sass files. Because any Sass dependencies inside the entry file are handled by my plugin and not Duo, I have to watch them myself for changes. I can do that, and I can perform a touch on the entry file, but the next time Duo builds something that depends on that file, it just uses the cached copy in duo.json.

Is this a bug? Is there a way to force Duo to recheck the mtime of a file?

[dominicbarnes]

Is this a case where sass is importing dependencies instead of duo? If so, it's tricky since there's no real way for duo to know about files it doesn't know about.

You can always use the --no-cache flag for situations like this, in case that helps you. Even better would be to allow duo to handle including those dependencies. (I don't know anything about sass, are they just @import rules that it processes? or does it have it's own syntax?)

[matthewmueller]

yah the caching is pretty awful atm. it needs to ignore files that haven't been changed, but still traverse their dependencies and check their mtimes.