Closed pbrisbin closed 1 year ago
+1, an unfortunate regression in the valuable --file-watch feature
@pbrisbin, thanks for reporting. You are experiencing the same problem as in https://github.com/commercialhaskell/stack/issues/5978, and the problem has been fixed in Stack's master
branch. If you want to get that Stack version now, stack upgrade --source-only --git
should build and install it.
Thank you @mpilgrem !
Awesome, thanks!
General summary/comments (optional)
I've noticed
stack
emitting a mess of unreadableshow
n exception data instead of a pretty error message in some cases. I was able to catch at least one instance just now, and realized it only happens with--file-watch
.Steps to reproduce
Example project:
stack.yaml and package.yaml
```yaml resolver: lts-20.10 extra-deps: - github: brendanhay/amazonka commit: f73a957d05f64863e867cf39d0db260718f0fadd # main, as of SSO support subdirs: - lib/amazonka - lib/amazonka-core - lib/services/amazonka-autoscaling - lib/services/amazonka-sqs - lib/services/amazonka-sso - lib/services/amazonka-sts ``` ```yaml name: agent version: 0.0.0.1 license: MIT dependencies: - base library: source-dirs: src dependencies: - Blammo - aeson - amazonka - amazonka-autoscaling - amazonka-sqs - bytestring - composition-extra - conduit - conduit-extra - data-default-class - envparse - errors - github - hedis - http-conduit - http-types - immortal - jwt - microlens-platform - monad-logger - monad-validate - optparse-applicative - relude - resourcet - tagged - text - time - tls - typed-process - unliftio - unliftio-core ```Expected
This is what you get without
--file-watch
,I should see the same.
Actual
This is what I see with
--file-watch
Stack version
Method of installation
Platform
Arch Linux