Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Clean up retained Data/List Viewer state for obsolete Interactive outputs

Ouverte
  • Quelque chose ne va pas ?
#1,838 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
r, typescript
Domaine
devtools

Piste de recherche

Start by reading the existing state_generation / dataview_dispose mechanism from #1741 and the dataview_set_state usage described in #1835. Trace how Interactive generations, retained history, and reconnects determine whether viewer state is still usable. Done means obsolete table and list viewer state is released when it can no longer be used, without breaking live or reconnectable outputs.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Background

This was identified during a ChatGPT-assisted review of #1835.

Interactive rich outputs retain R-side viewer state in .sess_env$dataviews so that notebook cells can continue paging or opening their full Data/List Viewer without serializing the complete object.

However, these states do not appear to be released when the corresponding Interactive output is no longer live.

For example, #1835 stores each plain list result with:

dataview_set_state(view_id, root)

and Interactive table outputs similarly retain Data Viewer state. Once an Interactive generation becomes archived, the extension correctly disables live controls, but the corresponding R-side state may remain referenced until the runtime itself is stopped.

This means old Interactive outputs can keep potentially large R objects alive even though they can no longer be browsed live.

Possible direction

Consider managing these states as Interactive-owned viewer resources, and dispose them when they can no longer be used, for example when:

  • an Interactive generation is replaced or restarted;
  • retained history is evicted;
  • an Interactive session/output is otherwise permanently discarded.

This should probably cover both existing table outputs and the list outputs introduced in #1835 rather than adding list-specific cleanup.

The existing state_generation / dataview_dispose mechanism from #1741 may provide the appropriate foundation, but Interactive output retention and reconnect semantics need to be taken into account.

Langage dominant
TypeScript
Étoiles
1.2k
Forks
147
Merge moyen
1 j 10 h
PR mergées (30 j)
64

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de REditorSupport/vscode-R

Toutes les issues de REditorSupport/vscode-R

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.