VRP gRPC: server-side validation of routing problem inputs
Open
@kaatish is already working on this.
Since Jul 28, 2026.
awaiting response
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 233
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 95
Description
Follow-up to #1597 (review nice-to-have #6). cpu_routing_problem::to_device validates capacity-dimension sizes but not cost/transit matrices or other array lengths. A malformed proto could pass sizes that data_model_view documents but does not hard-validate, risking out-of-bounds access on device.
Scope
- Validate shapes/lengths in
to_device(or the mapper) and return a clearINVALID_ARGUMENTinstead of risking OOB:- cost/transit matrices ==
num_locations² - order arrays ==
num_orders; vehicle arrays ==fleet_size - pickup/delivery index bounds, break/matching/precedence indices
- cost/transit matrices ==
🤖 Generated with Claude Code
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.