Development Task
The scheduler config and scheduler-related API paths under pkg/schedule/schedulers may panic or return inaccurate HTTP errors when receiving malformed or unexpected input.
Typical risky cases include:
- unsafe type assertions on scheduler config fields parsed from JSON
- unexpected scheduler type casts in transfer witness handling
- incorrect HTTP status codes for invalid user input
- nil-response handling gaps in scheduler API error paths
This task tracks hardening those code paths so that invalid input is rejected safely with clear client-facing errors instead of causing runtime panics or misleading 5xx responses.
Related work:
Development Task
The scheduler config and scheduler-related API paths under
pkg/schedule/schedulersmay panic or return inaccurate HTTP errors when receiving malformed or unexpected input.Typical risky cases include:
This task tracks hardening those code paths so that invalid input is rejected safely with clear client-facing errors instead of causing runtime panics or misleading 5xx responses.
Related work: