kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

feat(silo): push DAG on save and commit hooks #216

New Issue
Closed
opened 2026-02-14 19:40:31 +00:00 by forbes · 0 comments
forbes commented 2026-02-14 19:40:31 +00:00
Owner
Copy Link

Summary

Wire the DAG extraction engine into Silo_Save and Silo_Commit so the feature tree is pushed to Silo whenever the user saves or creates a revision.

Deliverables

  1. In Silo_Save.activated(): after successful file upload, call extract_dag(doc) and client.push_dag().
  2. In Silo_Commit.activated(): after revision creation succeeds, push DAG with the new revision number.
  3. Handle errors gracefully -- DAG push failure should warn but not block the save/commit.
  4. Log DAG sync result (node_count, edge_count) to console.

Location

mods/silo/freecad/silo_commands.py -- modify Silo_Save and Silo_Commit commands.

Depends on

  • DAG extraction engine issue
  • Client DAG API methods issue

Ref

docs/MULTI_USER_CLIENT.md Section 5

## Summary Wire the DAG extraction engine into `Silo_Save` and `Silo_Commit` so the feature tree is pushed to Silo whenever the user saves or creates a revision. ## Deliverables 1. In `Silo_Save.activated()`: after successful file upload, call `extract_dag(doc)` and `client.push_dag()`. 2. In `Silo_Commit.activated()`: after revision creation succeeds, push DAG with the new revision number. 3. Handle errors gracefully -- DAG push failure should warn but not block the save/commit. 4. Log DAG sync result (node_count, edge_count) to console. ## Location `mods/silo/freecad/silo_commands.py` -- modify `Silo_Save` and `Silo_Commit` commands. ## Depends on - DAG extraction engine issue - Client DAG API methods issue ## Ref `docs/MULTI_USER_CLIENT.md` Section 5
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
UX
branding
bug
ci/cd
CI/CD workflows and deployment
 defaults
documentation
Developer documentation
 enhancement
high-priority
low-priority
theme
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
forbes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/create#216
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?