Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
File is walked but then later removed and never re-walked #522
I'm currently running into an issue in
Here's the code that gives me a problem:
... At what point do the files get re-processed? because it looks to me like each file is walked once, its dependencies all inspected on its walking, and then THAT'S IT. This looks like code that just nixes a file entirely if nothing else references it as a dependency?
My file situation is as follows:
This doesn't seem too weird to me here, but I thought it was useful to include what the dep graph might look like.
In my various debugging attempts, I did a lot of in-module
Here's a stacktrace:
If I comment out the removal code, this error goes away and things seem to work as intended, but I'm not 100% sure what the side effects are of eliminating that chunk of code happen to be.
Let me know if you need any more information!
I think a better approach would be to not remove files by default, and instead only remove them if you pass a