Skip to content

VRP gRPC: log streaming and incumbent parity with LP/MILP #1630

Description

@ramakrishnap-nv

Follow-up to #1597. The LP/MILP gRPC path exposes log streaming and incumbent retrieval; VRP has submit/status/wait/cancel/delete but no log streaming or incumbents.

Scope

  • Wire routing solver logs through the server log pipe and expose them via the client (stream_logs/fetch_logs), as LP/MIP do.
  • Expose best-so-far routing solutions as incumbents if the routing solver supports intermediate results.
  • Decide whether a one-shot server-side solve_vrp is wanted (the Python client currently drives submit → wait → result; LP/MIP have solve_* one-shots) — document the choice.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

Labels

awaiting responseThis expects a response from maintainer or contributor depending on who requested in last comment.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions