repl :reload no longer reloads repl-overlays or :add'd expressions #1115
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
awaiting
author
awaiting
contributors
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1115
Loading…
Add table
Add a link
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?
Describe the bug
Before, given some
foo.nixfile:Then adding it, either in a repl overlay or with
:add:Then modifying that file:
And finally
:reloading the repl:would propagate the changes in the file to the repl state. Now, however, the repl does nothing for these cases:
nix --versionoutputAdditional context
Presumably this is a logic error in our and @raito's changes, somewhere in the chain of
43434d675e,7be72ca667,0f1208c406,f4be01b4be, and6cbbe19b5cI wonder if this is really a logical error, how do we track the existence of that
importto reload it? Should we reload the whole eval state all the time assuming there might be imports hidden? Tough…Do we really lose anything by reloading the whole eval state?
@qyriad if the whole eval state reload fails, we have trashed the eval state, maybe if we can back up it…