You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #1597 (unary-only VRP POC). The worker currently rejects chunked VRP, so a large cost/transit matrix or a RoutingSolution that exceeds the gRPC max message size can't be sent or retrieved.
Scope
Implement chunked upload (StartChunkedUpload/SendArrayChunk) for VRP problem arrays and chunked download (StartChunkedDownload/GetResultChunk) for RoutingSolution, mirroring the LP/MIP chunked path.
Add a client-side preflight size check so an oversized unary submit gives a clear early error or auto-falls-back to chunking instead of an opaque RESOURCE_EXHAUSTED (review nice-to-have [FEA] Add changed constraints logic in multiprobe #7).
Follow-up to #1597 (unary-only VRP POC). The worker currently rejects chunked VRP, so a large cost/transit matrix or a
RoutingSolutionthat exceeds the gRPC max message size can't be sent or retrieved.Scope
StartChunkedUpload/SendArrayChunk) for VRP problem arrays and chunked download (StartChunkedDownload/GetResultChunk) forRoutingSolution, mirroring the LP/MIP chunked path.RESOURCE_EXHAUSTED(review nice-to-have [FEA] Add changed constraints logic in multiprobe #7).Notes
result_total_bytesfix landed in Routing over gRPC: VRP server + compiled C++/Cython client #1597 (data_sizenow reflects the VRP header payload, so the oversized-result guard is meaningful).🤖 Generated with Claude Code