Skip to content

fix(#31,#34): surface sync failures — no false ✓ on LLM error, error in apc status - #59

Open
forge-fz2000 wants to merge 2 commits into
mainfrom
fix/issue-31-34-sync-failure-reporting
Open

forge-fz2000 wants to merge 2 commits into
mainfrom
fix/issue-31-34-sync-failure-reporting

Conversation

@forge-fz2000

Copy link
Copy Markdown
Collaborator

Fixes #31
Fixes #34

What changed

#31 — Misleading ✓ on LLM memory failure:

  • apply_memory_via_llm() now returns -1 (instead of 0) when the LLM call fails
  • Callers detect the -1 signal and show ✗ error instead of ✓ N memory files
  • Manifest is saved with last_sync_result='error'

#34 — apc status shows synced after crash:

  • ToolManifest gains save_failure(msg) which writes last_sync_result='error' to disk
  • sync_all() calls save_failure() in the except handler so hard crashes are recorded
  • _tool_sync_status() in status.py returns 'error' when last_sync_result=='error'
  • tools_status_table() renders ✗ error in red for failed tools

Tests

Updated three test assertions that expected 0 on LLM failure; they now expect -1.

…status in apc status

Issue #31: apply_memory_via_llm() now returns -1 (not 0) when the LLM
call fails. Callers (sync_memory, sync_all) detect the -1 signal and
show an error line instead of a ✓ success indicator, and save the
manifest with last_sync_result='error' so the failure is persisted.

Issue #34: ToolManifest gains save_failure(msg) which writes
last_sync_result='error' to disk. sync_all() calls save_failure() in
the except handler so that even a hard crash (e.g. [Errno 17] symlink)
is reflected in the next apc status check. _tool_sync_status() in
status.py returns 'error' when last_sync_result=='error', displayed as
'✗ error' in the tools table.

Tests updated to expect -1 from apply_memory_via_llm on LLM failure.

@FZ2000 FZ2000 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be a docker test for this.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants