"target/debug/deps" grows every time run task run-book
#2566
Comments
richb-hanover
changed the title
task run-booktask run-book
|
56GB is extreme! Unfortunately I think this is because of both cargo and #1836, and there's no particularly easy way to solve it. But:
|
eitsupi
changed the title
task run-booktask run-book
|
Thanks for these thoughts. It doesn't seem there's much to do about rebuilding right now. I can live with it. re: size of |
|
@max-sixty , @eitsupi Sorry for necro-posting - please let me know if this is the same thing we discussed back in May... I recently removed all containers, images, and volumes from Docker, and In particular, I see multiple builds of liblibduckdb_sys and prqlc (and many others), separated in time by a few minutes or hours. It feels to me as if these builds are not being cached. Is this the same cause as earlier? Should I create a separate issue? What other information could I provide? Thanks as always. Expand the "Details" to see the |
|
I'm not sure what's going on here. This might be more of a cargo problem than a PRQL problem, although we're keen to help with anything that facilitates your PRQL work. Does running |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Every time I quit VS Code, re-launch it, then run
task run-book, the Dev Container rebuilds a lot of stuff. This happens even if no changes have been made to the source files. This takes a couple minutes on my fairly modern Macbook, so it's annoying. (It's OK if I ^C the command and re-run. No rebuild is necessary until I quit VS Code.)BUT... the size of the target/debug/deps directory continually increases. At the moment it occupies 56 GB (!) on my computer. When I look at the contents of the folder, I see a large number of ~250MByte
mdbook_prql-24440258aa393249files with dating back to March. (See below.) In fact, each item in the "Compiling" list above generates one of those files).My questions:
Many thanks
PRQL input
SQL output
N/AExpected SQL output
N/AMVCE confirmation
Anything else?
No response
The text was updated successfully, but these errors were encountered: