__json can be invalid without the daemon rejecting the derivation, then fails at build #380
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#380
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?
cc @puck
initially i was thinking we shouldn't accept people putting
__json
into derivations at all, but I'm not so sure now. i think that has possible valid use cases like wanting to serialize it in another process and avoid a round trip, perhaps, but we could certainly just outright reject derivations with bad__json
as invalid at the daemon, assuming that uh we actually have any checks on those and they're not just like, sent over as bytes as it currently stands.