posit-dev / posit-dev/positron

R DataFrame Output Not Persisted After Reopening Notebook

Open
#12,977 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: notebooks-jupyter lang: r
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

Description

Observation

There is an issue and difference in behavior between data frame created by Python vs. R. Logging an issue for that.

Repro:

  1. Upon running the cell, data frame is displayed, as expected.
  2. However, if user closes the notebook file and then returns to it, notice that the data frame output for the R cell will NOT load.
  3. Instead, it will state "Data unavailable. Re-run cell to view". This is different from the Python cell behavior, which retains the data frame output despite user closing and re-opening the file (despite of saving or not saving).
Image

Originally posted by @rodrigosf672 in #12061


Summary

R data frame outputs are not persisted after closing and reopening a notebook, unlike Python data frames which remain visible.

Repro Steps
  1. Run a cell that creates and displays a data frame (in both Python and R).
  2. Close the notebook file.
  3. Reopen the notebook.
Expected Behavior

Data frame outputs should persist and be visible without re-running cells (consistent with Python behavior).

Actual Behavior
  • Python: Output persists as expected.
  • R: Output shows “Data unavailable. Re-run cell to view.”
Impact

Inconsistent cross-language behavior; disrupts workflow for R users.


Positron Version: 2026.05.0 build 30
Code - OSS Version: 1.109.2
Commit: d2bce05424152f00e9164e2ea655d53d32e6e232
Date: 2026-04-09T07:51:26.722Z
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

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.

Research direction

No source file or test is named. Start by reproducing the notebook behavior with equivalent Python and R data-frame cells, then trace how their outputs are restored after reopening; done means the R output remains visible without rerunning, matching Python behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, r
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.