Diagnose system hangs and dropped message flows in MeshWeaver actor-model architecture.
npx skills add https://github.com/Systemorph/MeshWeaver --skill debug-systemorph
Please help me install this Agent Skill. Skill: debug Source: https://github.com/Systemorph/MeshWeaver/tree/main/.claude/skills/debug Command: npx skills add https://github.com/Systemorph/MeshWeaver --skill debug-systemorph
This Skill resolves complex system hangs, timeouts, and deadlocks in the MeshWeaver framework by identifying the exact broken edge in the message flow where communication stops.
Use the debug skill to analyze the trace log at /tmp/trace.log and identify the last successful message flow tag.
High-intent search queries and answers about installing and using this skill.
Message flow deadlocks in the MeshWeaver actor model are diagnosed by analyzing structured logs and correlating trace tags to isolate the exact broken edge where communication stops. This pinpoints dropped messages or failed handlers causing system hangs.
Test suite hangs during CI execution under high load often stem from cross-test interactions or grain deactivation races. Trace the last successful message flow tag to determine if a missed reactive observation or a genuine system lock is causing the interruption.
Dropped reactive emissions during high-load execution are traced by performing structured log analysis to map the message delivery pipeline. You identify the specific broken edge by correlating trace tags to see where the reactive observation was missed.
Reproducing intermittent cross-test interactions that only occur under full-suite load requires bulk reproduction methodology. This approach targets the specific conditions triggering grain deactivation races and message flow interruptions during high-load execution.
Trace-tag correlation is used to isolate grain deactivation races by mapping the message delivery pipeline. By tracing message tags through structured logs, you can identify exactly where a grain deactivated prematurely and dropped a reactive emission.
Debugging system hangs without structured log analysis prevents effective trace-tag correlation, making it nearly impossible to isolate the specific broken edge in the message delivery pipeline. You cannot accurately determine if the issue is a missed reactive observation or a genuine deadlock.
roromanenkoEnforce consistent log levels, templates, and correlation scopes for NewsParser code.
g-zenrGenerates performance and load tests for API throughput, thread safety, and rate limiting.
SystemorphDiagnose reactive storms causing MeshWeaver portal outages from Kubernetes pod logs.
unju-aiImplement thread-safe Swift data persistence using actors for caching and file storage.
