arcana/arcana
0
0
Fork 2
Code Issues 20 Pull requests 7 Projects Releases 1 Packages Wiki Activity Actions 7

Let command execution take place without control interpretation #36

New issue
Open
opened 2026-01-10 15:36:02 +00:00 by raito · 0 comments
raito commented 2026-01-10 15:36:02 +00:00
Owner
Copy link

If you run two nix build in a build, via tx, the headed response protocol logic will parse two store paths emitted and result in a panic.

This is wrong, we should separate logging from control interpretation. We should be able to log things without having them be the final result for a given command.

If you run two nix build in a build, via tx, the headed response protocol logic will parse two store paths emitted and result in a panic. This is wrong, we should separate logging from control interpretation. We should be able to log things without having them be the final result for a given command.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
build-on-target
ci
custom-toplevels
rewrite-arcana-base-server
feature/custom-activation
feature/colmena-nix-darwin-server
feature/colmena-netconf-server
feature/colmena-liminix-server
fix-eval
cleanup
fix-filtering
nix-defined-activation
v0.6.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
arcana/arcana#36
No description provided.