maaend-issue-log-analysis

Analyze MaaEnd issue logs by fetching MaaEnd-logs-*.zip attachments from GitHub issues, decompressing them, and cross-referencing logs like maa.log and mxu-tauri.log with documentation to pinpoint root causes. This extracts evidence to identify task stalls and pipeline failures.

Extracting diagnostic evidence from MaaEnd-logs involves decompressing the zip file and parsing key logs such as go-service.log, mxu-web-*.log, and on_error/ directories. This process surfaces timelines, controller mismatches, and task names for root cause analysis.

Yes, you can use a GitHub issue URL to automatically diagnose MaaFramework pipeline failures. Providing the issue URL allows the workflow to automatically fetch and extract log artifacts to identify version, controller, and task name details for remediation.

Troubleshooting MXU controller mismatches requires log files like maa.log, go-service.log, mxu-tauri.log, mxu-agent*.log, and on_error/ directories. These logs are cross-referenced with MaaEnd and MaaFramework documentation to derive actionable fixes for misrecognition issues.

MaaEnd issue analysis fails when the MaaEnd-logs attachment is missing because the workflow relies on decompressing MaaEnd-logs-*.zip to extract evidence from logs like maa.log. Without these logs, it cannot cross-reference documentation to produce a structured diagnostic report.

The best way to generate a structured diagnostic report for MaaEnd issues is to normalize inputs, extract timelines from logs, and cross-reference evidence with MaaEnd, MaaFramework, and MXU documentation. This produces a consolidated report with validated evidence and recommended fixes.