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
[bug] .env
file specified in envFile
option is cached
#896
Comments
@shellscape If you use I also tested this on our 1.8 branch and it's working as expected. We did so some heavy migration as part of 1.8, so this was probably inadvertently fixed. |
Sorry for the delay, was out of town for a bit. This is on my list to test on 1.8 later today. |
This was reworked again in 1.9, can you give it a look. |
On it. |
@milesj this is still a problem with 1.9.1 |
Ok dug into it more. It's because tasks are expanded when added to the project graph, and then the graph is cached entirely. So subsequent runs are hitting the cache. This'll take some time to fix. |
Fixed in v1.11 https://moonrepo.dev/blog/moon-v1.11 |
DOPE. |
Describe the bug
It appears that a
.env
file specified in theenvFile
options is being cached.Steps to reproduce
Create a
.env
file with:Create a task:
Create
scripts/echo.ts
:moon run root:batman
robin
joker
moon run root:batman -u
robin
moon run root:batman --cache off
joker
I'm able to consistently reproduce this in a fresh repo as well as the existing repo.
Expected behavior
.env
files should not be cached, nor considered part of any task cache.What's also troubling is that the
cache: false
option is specified, but appears to be ignored.-u
has no effect but--cache off
does have an affect.Screenshots
n/a
Environment
Additional context
This is something new since migrating from 1.2 to 1.7.x, so this looks like a regression or a breaking change in a minor.
As an aside, it might be helpful to spin up triage environments that people can fork for reproductions. This is what we setup for rollup https://stackblitz.com/fork/rollup-repro and https://repl.it/@rollup/rollup-plugin-repro
The text was updated successfully, but these errors were encountered: