[checkpoint] Restore example MCP weather call history

Open
#3,233 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

Start with resources_servers/example_mcp_weather/app.py and the parent issues #3219 and #3024; identify how the expected city and ordered weather-call history are used by verification. Done means the listed restore, isolation, fencing, corruption, revision, replacement, and idempotent cleanup acceptance criteria all pass.

Written by the indexing model from the issue text.

Description

area:environment feature

Parent

Child of #3219 and #3024.

Problem and state owner

resources_servers/example_mcp_weather/app.py owns the expected city and ordered weather-call history required by verification.

Proposed adapter

Persist expected city and ordered {city, weather} records, then bind the replacement execution to a fresh local session.

Implement explicit checkpoint opt-in, route classification, export/restore/retire hooks, execution-to-session binding, revision reporting, atomic replacement under attempt N+1, and stale-attempt fencing.

Acceptance criteria

  • A call followed by restore verifies successfully; a no-call snapshot still fails verification and concurrent sessions remain isolated.
  • Checkpoint after multiple mutations, replace the server process, restore, and compare the next operation with an uninterrupted execution.
  • Corrupt or incomplete bulk state activates no sessions.
  • Attempt N cannot mutate or retire restored attempt N+1.
  • Terminal cleanup is idempotent and releases restored state exactly once.
Dominant language
Python
Stars
1.2k
Forks
349
Avg merge
1d 21h
Merged PRs (30d)
318

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.

More from NVIDIA-NeMo/Gym

All issues in NVIDIA-NeMo/Gym

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.