Cache question: Rendered template is not change even if the .stpl file is changed

I'm on Windows, I'm not sure this is a known behaviour from the lib, or is there anyway that we can always clear cache when in development, and only enable it in production?
Thanks

[dodalovicgran]

same issue here

[vthg2themax]

I don't normally use a windows box for development, so I had to setup a virtual machine for this with Windows 11 Pro 64 bit to test if I can reproduce. I was unable to reproduce, but with 2 reports, I am willing to look into this further. Can you share a sample bit of code, or project with a minimum amount needed to build, that I can replicate this behavior? @rhacker @dodalovicgran

@vthg2themax i think it's the normal behavior of the lib when we use template once. the pre-rendered template is in an out folder of compiler. what i ask is if there is any other way that only enable this default behavior only in production ( through env var )

[aalowlevel]

Any progress on this problem? This keeps me from upgrading from ~0.7.0

[vthg2themax]

@rhacker @aalowlevel Does this change help out any?

@vthg2themax thanks for the update, I will check the latest update to see if it works in my case.

@vthg2themax I didn't have time to go through the changes, however, the new merge, the compiler breaks some working parts in my application. I will need time to go through the change in the compiler to see what's wrong.

[vthg2themax]

@rhacker Thank you very much for looking into this! I tested it with my site first, (which to be fair isn't very complicated), and it didn't seem to cause an issue, so if you have any pointers for it, I'd very much appreciate any information you would be willing to share.

[aalowlevel]

@vthg2themax @rhacker

error: proc-macro derive panicked --> {..} | 6 | #[derive(TemplateOnce, Clone, Default, Debug)] | ^^^^^^^^^^^^ | = help: message: Lock file "{..}\\target\\debug\\build\\sailfish-compiler-fb8e9dce29b49683\\out\\templates\\{..}.lock" is stuck. Try deleting it.

[nwtnni]

I can also help debug if we can get some more information about what broke.

@aalowlevel, do you get the same error after deleting the lock file and/or after running cargo clean?

[aalowlevel]

@nwtnni No.

[PaulDotSH]

It is working fine on linux on 0.8.3

[PaulDotSH]

It is working fine on linux on 0.8.3

I just got this same problem randomly, I couldn't reproduce it though, if anyone finds reproduction steps I would be open for a PR