Skip to content

Use the full snapshot scope by default for the counter demo#520

Open
Michael Shen (mjlshen) wants to merge 1 commit into
agent-substrate:mainfrom
mjlshen:counter/onCommit-full
Open

Use the full snapshot scope by default for the counter demo#520
Michael Shen (mjlshen) wants to merge 1 commit into
agent-substrate:mainfrom
mjlshen:counter/onCommit-full

Conversation

@mjlshen

@mjlshen Michael Shen (mjlshen) commented Jul 24, 2026

Copy link
Copy Markdown

The Data snapshot scope is meant to restore state from DurableDir volumes and does not persist the process memory. For this demo, it makes more sense to default to the Full snapshot scope so that users can play around with incrementing a counter, pausing/resuming with the previous value still intact, and continue incrementing the counter.

Fixes #519

  • Tests pass
  • Appropriate changes to documentation are included in the PR

The Data snapshot scope is meant to restore state from DurableDir
volumes and does not persist the process memory. For this demo, it makes
more sense to default to the Full snapshot scope.
@mjlshen Michael Shen (mjlshen) changed the title Fix counter memory preservation on suspend Use the full snapshot scope by default for the counter demo Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Counter demo: in-memory state not preserved across suspend/resume (gVisor, kind), despite onPause: Full

1 participant