better UX for cached evaluation failures #223
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#223
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is your feature request related to a problem? Please describe.
As a user I might run a command and see the error
error: cached failure of attribute '<...>'
I might not remember why this failed the last time.
For new users, this situation can be very frustrating, because they do not know how to get the information why this command fails.
Describe the solution you'd like
Best would be to save the error to the eval cache, and show it together with a hint that this is from a cached failure.
Describe alternatives you've considered
I'm currently just adding
--impure
to force re-evaluation. Adding an accompanying hint to the cached failure message would also be an improvement.Additional context
N/A
Btw you can force re-evaluation with
--no-eval-cache
or--option eval-cache false
. However. I would like to kill this with fire.Is there any reason to cache failures in first place honestly??
none that can be reasonably argued for; in a perfectly deterministic evaluator (which we do not have!) it would make sense though. we should just remove the failure cache entirely, the eval success cache is already sketchy and the eval failure cache even more so
https://gerrit.lix.systems/c/lix/+/771