Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#1,838 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
r, typescript
Bereich
devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1.2k
Forks
151
Ø Merge
1 T. 8 Std.
Gemergte PRs (30 T.)
76

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus REditorSupport/vscode-R

Alle Issues in REditorSupport/vscode-R

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.