NVIDIA / NVIDIA/cuopt

VRP gRPC client completeness: settings surface, e2e coverage, docs, perf nits

Open
#1,632 3 comments 0 reactions 1 assignee View on GitHub

@rg20 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-haves #5, #8, #9 + docs).

Settings surface (#9)
  • The Python RoutingClient forwards only time_limit; map the rest of RoutingSolverSettings (verbose, error_logging, dump_best_results_path/interval) for parity.
E2E coverage (#5)
  • The live test covers only a small cost-matrix problem; add capacity and time-window remote-vs-local cases (gated on CUOPT_GRPC_SERVER).
Perf / robustness nits (#8)
  • _solution_to_py: take the solution by const ref.
  • Consider bulk RepeatedField assignment and releasing the GIL in the wait loop.
  • Revisit the test-driver message-size limits.
Docs
  • Document cuopt.grpc.routing.RoutingClient as the GPU-less remote entry point in the package/API docs.

🤖 Generated with Claude Code

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.