fix(discovery): catch ConfigError per-job in discover_jobs #127
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/kronai!127
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/0080-handle-invalid-job-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Wrap
load_job_configintry/except ConfigErrorper-job so that an invalidconfig.tomlin one job doesn't halt discovery of all other jobs.Why
One bad config should not block everything — it falls back to defaults and continues.
Testing
Closes #80
Automated Review — PR #127
Result: APPROVED
Clean fix — wraps
load_job_config()intry/except ConfigErrorper-job, falling back toJobConfig()defaults with a warning. Prevents one bad config from blocking discovery of all other jobs. Closes #80.No suggestions.