VRP gRPC: log streaming and incumbent parity with LP/MILP
Open
@tmckayus 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. 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_vrpis wanted (the Python client currently drives submit → wait → result; LP/MIP havesolve_*one-shots) — document the choice.
🤖 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.