pub enum TaskError {
IO(String),
Handle(String),
Channel(String),
InvalidConfiguration(String),
}Expand description
Errors that can occur during task configuration and execution
TaskError represents all error conditions that can arise when configuring,
validating, or executing tasks. Each variant provides specific context
about the failure to enable proper error handling and debugging.
§Examples
§Error Handling
use tcrm_task::tasks::{config::TaskConfig, error::TaskError};
fn validate_config(config: &TaskConfig) -> Result<(), String> {
match config.validate() {
Ok(()) => Ok(()),
Err(TaskError::InvalidConfiguration(msg)) => {
Err(format!("Configuration error: {}", msg))
}
Err(TaskError::IO(msg)) => {
Err(format!("IO error: {}", msg))
}
Err(other) => {
Err(format!("Other error: {}", other))
}
}
}§Pattern Matching on Events
use tcrm_task::tasks::{event::TaskEvent, error::TaskError};
fn handle_event(event: TaskEvent) {
match event {
TaskEvent::Error { task_name, error } => {
match error {
TaskError::IO(msg) => {
eprintln!("Task '{}' IO error: {}", task_name, msg);
}
TaskError::InvalidConfiguration(msg) => {
eprintln!("Task '{}' config error: {}", task_name, msg);
}
TaskError::Channel(msg) => {
eprintln!("Task '{}' channel error: {}", task_name, msg);
}
_ => {
eprintln!("Task '{}' error: {}", task_name, error);
}
}
}
_ => {}
}
}Variants§
IO(String)
Input/Output operation failed
Covers file system operations, process spawning failures, and other system-level IO errors.
§Common Causes
- Command not found in PATH
- Permission denied when spawning process
- Working directory doesn’t exist or isn’t accessible
- File descriptor or pipe creation failures
Handle(String)
Process handle or watcher error
Errors related to process handle management or watcher failures.
§Common Causes
- Failed to obtain process ID after spawning
- Watcher task join or abort errors
Channel(String)
Inter-task communication channel error
Failures in the async channel system used for event delivery, stdin input, or process coordination.
§Common Causes
- Event channel closed unexpectedly
- Stdin channel disconnected
- Termination signal channel closed
- Receiver dropped before sender finished
InvalidConfiguration(String)
Task configuration validation failed
The task configuration contains invalid parameters that prevent safe execution. Always check these before starting tasks.
§Common Causes
- Empty command string
- Invalid characters in command or arguments
- Working directory doesn’t exist
- Environment variables with invalid keys
- Zero or negative timeout values
- Security validation failures (command injection, etc.)