fix(scheduler): report total working memory count in log_working_memory_replacement#1795
Conversation
87a8081 to
8ef020e
Compare
|
All 16 build matrix legs were failing identically. Investigated the ubuntu-latest/3.11 job log: Root cause: this was caused by my diff, not an unrelated base-branch breakage. The new Fix: ran
This should resolve all 16 failing build legs. |
|
Hi, just following up — CI has been green since the ruff format fix on June 17. Let me know if there's anything you'd like changed before merging! |
|
Automated Test Results: PASSED Cloud test-engine rerun against
Manual code review is still required before merge. |
Description
log_working_memory_replacementwas passingmemory_len=len(memcube_content)wherememcube_contentonly contains newly added memories. This caused the scheduler UI to show the delta count instead of the total working memory size after replacement.Fix: use
len(new_memory)to report the actual output count.Related Issue (Required): Fixes #1790
Type of change
How Has This Been Tested?
Checklist