runtime-errors

Diagnose runtime errors in Sirius queries by analyzing logs and running targeted debug workflows.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/kindofluke/albatross-data --skill runtime-errors-kindofluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-errors
Source: https://github.com/kindofluke/albatross-data/tree/main/.vibe/skills/runtime-errors
Command: npx skills add https://github.com/kindofluke/albatross-data --skill runtime-errors-kindofluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and triage runtime-errors in Sirius-driven queries, including crashes, segfaults, exceptions, hangs, or unintended CPU fallbacks, by analyzing logs and orchestrating targeted debugging workflows.

Core Features & Use Cases

  • Automated error classification: Identify type of failure (hang, segfault, runtime error) from logs and runtime traces.
  • Multi-path debugging: Provides specialized workflows (hang-path, segfault-path, runtime-error-path) with guided steps and logging strategies.
  • Integrated tooling: Suggests usage of SIRIUS_LOG logging, cuda-gdb, and NVIDIA Compute Sanitizer to reproduce and fix issues.

Quick Start

Run the Runtime Error Analyzer with your SQL query and an optional timeout to reproduce the issue and collect actionable diagnostics.

Frequently Asked Questions about runtime-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose runtime errors and segfaults in Sirius workloads?

Diagnose runtime errors in Sirius by analyzing logs, inserting targeted debug markers, and re-running queries to identify application crashes, hangs, or unexpected CPU fallbacks.

What is the best way to debug a Sirius query hang?

Debug a Sirius query hang using the Hang Path workflow, which provides guided triage steps, structured logging strategies, and optional timeout parameters to reproduce and isolate the issue.

Can I use cuda-gdb and Compute Sanitizer to troubleshoot Sirius runtime exceptions?

Yes, you can troubleshoot Sirius runtime exceptions using integrated tooling like cuda-gdb and NVIDIA Compute Sanitizer to reproduce failures and collect actionable diagnostics.

How do I find why my Sirius workload falls back to CPU unexpectedly?

Identify unexpected CPU fallbacks in Sirius by analyzing structured logs and runtime traces to classify the failure type and guide phase-based triage with concrete logging steps.

Does the Sirius runtime error analyzer require specific logging configurations?

The analyzer uses a YAML-driven frontmatter and leverages SIRIUS_LOG logging to classify failures and orchestrate specialized debugging workflows across Hang, Segfault, and Runtime Error paths.

What are the limitations when debugging Sirius segmentation faults?

Debugging Sirius segmentation faults requires re-running queries with targeted debug markers and external tools like cuda-gdb, which may involve complex setup and extended reproduction times.