You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first ~dozen are fast, but eventually it slows down.
I ran stack -v build. Below are all the debug messages between three of the "> using precompiled package" lines. (The entire output is also attached). If you look at the timestamps, indexed-traversable is obviously fast, and ansi-terminal is very slow by comparison.
All of the other slow packages also have a bunch of debug output and sqlite activity.
This behavior showed up unexpectedly when I changed one of my dependencies. I added an extra-dep that overrode version of amazonka that was being used from the snapshot. Although this won't help with repro, I'll show the change that triggered the behavior for context:
extra-deps:
# <snip>
# This amazonka includes the unreleased patch to support Cloudflare, which kinda
# has a bug. See https://github.com/brendanhay/amazonka/issues/975 for details.
- github: brendanhay/amazonka
commit: '85e0289f8dc23c54b00f7f1a09845be7e032a1eb'
subdirs:
# This has the patch
- lib/amazonka-core
# This one has a build failure if taken from lts-22.7
- lib/services/amazonka-s3
+ # Same + - lib/amazonka
Before that change, the project built quickly and didn't print any "using precompiled package" messages, slowly or otherwise.
@chreekat, I don't know about speed, not least because Stack is likely doing things in different threads and that makes the interleaved debug output difficult to unpick, but I think Stack is behaving as expected, as follows:
by changing a (deemed) immutable extra-dep, you are specifying a new cache in the snapshot directory of the Stack root; and
Stack is working out what it can re-use from other existing caches and copying from those caches to the new cache. It announces it is doing that with using precompiled package.
For example, building Stack itself, if I add acme-missles-0.3 as a (redundant) extra-dep, the build initially speeds though a number of using precompiled package until it hits open-browser-0.2.1.0 (which package, a direct dependency, for some reason, Stack decides it needs to build). While it is building that package in one thread, it continues to use some further using precompiled package (but a little slower than before). It then hits other packages Stack decides it needs to build: bitvec, indexed-traversable-instances, rio, serialise, text-metrics, th-lift-instances, hackage-security, semialign, witherable ... and things slow down.
The first ~dozen are fast, but eventually it slows down.
I ran
stack -v build
. Below are all the debug messages between three of the "> using precompiled package" lines. (The entire output is also attached). If you look at the timestamps,indexed-traversable
is obviously fast, andansi-terminal
is very slow by comparison.All of the other slow packages also have a bunch of debug output and sqlite activity.
This behavior showed up unexpectedly when I changed one of my dependencies. I added an extra-dep that overrode version of
amazonka
that was being used from the snapshot. Although this won't help with repro, I'll show the change that triggered the behavior for context:Before that change, the project built quickly and didn't print any "using precompiled package" messages, slowly or otherwise.
Here's the log "snippet":
Stack version
Method of installation
NixOS package manager
Platform
NixOS 24.11.713790.2b4230bf03de (Vicuna)
The text was updated successfully, but these errors were encountered: