Documentation

Technical documentation for installing, configuring, and running the Pyvorin compiler.

Filtered by category: Debugging. Clear filter

Debugging

Pyvorin provides several tools for diagnosing problems without exposing secrets or source code. pyvorin doctorpyvorin doctorChecks Python version and platform support, network reachability to the Portal, licence and device token validity, and configuration file syntax. Compile logspyvorin compile app.py --verboseVerbose mode prints per-module compilation status, fallback reasons, and timing. Logs are stored locally and are not uploaded unless telemetry is enabled. Reporting bugspyvorin report-bug --title "Unexpected fallback" --logsThis creates a support ticket. By default, source code is not attached, command text is redacted, and stack traces are included.

Updated 1 month ago

Debugging

Reading Compile Logs

Compile logs are stored in the Pyvorin data directory on your machine. Each log entry includes the command hash, compile status, duration, native coverage, and fallback reasons. Logs do not contain source code unless you explicitly opt in. Use pyvorin logs to list recent logs and pyvorin logs --tail to view the most recent entries.

Updated 1 month ago

Debugging

Verbose Output

Run compiles with --verbose to see detailed progress. pyvorin compile app.py --verbose Verbose output shows each compiled module, fallback decisions, and timing. This is useful when a compile fails or produces unexpected fallback results.

Updated 1 month ago

Debugging

Report Bug Command

The report-bug command opens a support ticket with useful diagnostics. pyvorin report-bug --title "Title" --logs By default, source code is not attached and command text is redacted. You can attach additional files manually after the ticket is created.

Updated 1 month ago