-
Notifications
You must be signed in to change notification settings - Fork 222
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
"target/debug/deps" continues to grow with continual re-compiles... #3427
Comments
Could we evaluate exactly:
A quick scan:
The next stage would be looking at the diffs in the file lists to see what gets produced, and trying with the playground, and then investigating exactly what actions cause what files to be created... |
Yes - that makes sense. I'll do that next and report back. Thanks. |
Dev Container behavior changed last night - the prql/target/debug/deps folder no longer seems to grow without bounds. (It's hovering around 2-4GBytes) Here's what I learned:
Here is the output prql/target/debug/deps. Expand the Details below. No new files are present from this morning; only those after the builds from last night Update: Edited lightly for clarity.
|
Thanks for the detail! So is it correct that (edit: aside from) #3336, this isn't an issue any longer, as far as we know? |
Here's a compilation of curiosities:
Thanks!
|
What does "I start the Dev Container" mean? |
(Sorry — I knew this and typo-ed above, now edited)
Dependencies are duplicated if they require different versions, which may contribute
Interesting (though only academically so given it's still 350MB :) ). These are debug builds, so possible are just not optimized and so big. But that is much higher than I would have expected. So I think the point that @eitsupi 's asked about is the remaining one from this issue |
Thanks for these comments. I believe there are two outstanding issues:
We are making tons of progress. (In particular, the 'growing target/debug/deps folder' seems to be solved.) I think we can close this. Thanks! |
What happened?
I'm reopening / reviving this issue because it slows my development work. I'll point to my updated report with a description of the
deps
directory after removing all the containers/images/volumes and rebuilding.What I see is:
task run-book
ortask run-playground-cached
.cargo install mdbook-admonish
on my Intel box (but @eitsupi has tracked down the cause of this.)This is annoying because:
main
to get the latest changes to the Bookrun-book
ornpm
cache updates.To respond to @max-sixty's question:
cargo clean
does empty out the deps folder, but then requires recompilation of a lot of stuff.This may not be our most important issue: I understand the workarounds, and don't feel the urge to update the Book any time soon. As always, please let me know what other information I could provide. Thanks.
PRQL input
SQL output
N/A
Expected SQL output
No response
MVCE confirmation
Anything else?
No response
The text was updated successfully, but these errors were encountered: