fix: federated learning memory leaks and stability #93
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses stability issues in the Federated Learning service.
1. Memory Leak Prevention
EphemeralLearningAgentaccumulated task history indefinitely until aggregation occurred. If the coordinator was offline or the interval failed, this caused unbounded memory growth.maxHistorySize(default 1000) cap. The history queue now automatically drops the oldest tasks when full.2. Process Lifecycle Management
FederatedLearningManagerstarted asetIntervalthat kept the Node.js event loop alive indefinitely, causing CLI commands and tests to hang instead of exiting..unref()to the aggregation timer, allowing the process to exit naturally when no other work is pending.Result: Safer, leak-proof distributed learning agents.