Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#1,838 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
r, typescript
Domínio
devtools

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
1.2k
Forks
151
Merge médio
21h 49min
PRs com merge (30d)
82

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de REditorSupport/vscode-R

Todas as issues de REditorSupport/vscode-R

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.