You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
append_log writes one log.md line per captured object and drowns the human changelog #43
append_log(bundle, f"Captured table: {name}") prepends a bullet under today’s heading for every object. A 67-item Fabric capture inserted ~60 timestamped “Captured dashboard/report/table/ingestion” lines above the narrative walk entry. The human changelog became unreadable.
Expected
Batch: one log line per CLI invocation with counts (Captured 11 tables, 20 semantic models).
Or append to .dekc/walk.log / WriteEvents, not knowledge/log.md.
Keep log.md for human/session summaries.
Code
Callers in dekc_capture.py / dekc_platform.py after each write_knowledge. Helper append_log in dekc_common.py.
Found on: DEKC 0.4.1 (GitHub Latest 2026-08-24), mixed PKC+SAC+DEKC second brain, Azure Fabric reverse-engineering walk. Not a sample-knowledge issue. Repro used live capture scripts from spillwave-second-brain cache data-engineering-knowledge-capture/0.4.1/.
Activity
fix: 0.4.2 Fabric walk issues (#26–#44)
RichardHightower commentedon Aug 25, 2026
Fixed in 0.4.2 via #45. Capture functions no longer append per-object
log.mdlines. One summary line per CLI invocation.