Error Handling Q&A
This document covers common error scenarios, edge cases, and troubleshooting steps for warpt.
Common CLI Errors
Type Mismatches
| Scenario | Example Command | Behavior |
|---|---|---|
| String where integer expected | warpt stress -d abc |
Error: Invalid value for '--duration' / '-d': 'abc' is not a valid integer. |
| Float where integer expected | warpt stress -d 5.5 |
Error: Invalid value for '--duration' / '-d': '5.5' is not a valid integer. |
| Negative duration | warpt stress -d -10 |
Error: Invalid value for '--duration' / '-d': -10 is not in the range x>=1. |
Invalid Choice Values
| Scenario | Example Command | Behavior |
|---|---|---|
| Invalid category | warpt stress -c bad |
Error: Unknown category 'bad'. Valid: accelerator, all, cpu, network, ram, storage |
| Invalid output format | warpt stress --format xyz |
Error: Invalid value for '--format' / '-f': 'xyz' is not one of 'json', 'yaml', 'text'. |
| Invalid benchmark | warpt benchmark run -b fake |
Error: Unknown benchmark 'fake'. Valid: HPLBenchmark |
Missing Arguments
| Scenario | Example Command | Behavior |
|---|---|---|
| Flag with no value | warpt stress -d |
Error: Option '-d' requires an argument. |
| Subcommand with no value | warpt stress -c |
Error: Option '-c' requires an argument. |
Troubleshooting Guide
Q: I'm seeing "CUDA_ERROR_OUT_OF_MEMORY". What should I do?
A: This occurs when the model or test workload is too large for your GPU's VRAM. Try reducing the workload size or offloading some layers to the CPU if applicable.
Q: Why is the CLI not responding to my input?
A: Ensure that you have a stable connection if using a remote provider. If running locally, check your system's resource usage. You can also try running with --verbose to see where the process is hanging.
Q: How do I reset my configuration?
A: You can run warpt config reset to restore default settings, or manually delete the config file located at ~/.config/warpt/config.toml.
Q: What does "Context Window Exceeded" mean?
A: The total amount of text (prompt + history + attached files) has surpassed the model's limit. Try removing unnecessary files from the context or using the --summarize flag.
Q: Why do I get "Permission Denied" for power monitoring?
A: On macOS, powermetrics requires sudo privileges. On Linux, you may need to be in the powercap group or run as root to access /sys/class/powercap/.