Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: vscode-R 3.0.1: code from other project files silently executed in R session via sess

Abierto
  • ¿Algo no está bien?
#1,877 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
12/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
r, typescript
Área
developer-experience

Línea de trabajo

Start by checking whether the foreign code comes from the session watcher: toggle the r.sessionWatcher setting and see if the stray assignments stop, then inspect the sess.workspace task callback registered via sess::.runtime_add_task_callback. The issue does not name a file in the extension to change, and the cause is unconfirmed. Done would mean a reproducible trigger is identified and the extension no longer executes code absent from the console or history. Expect the work to involve the R session interaction and the workspace viewer, which needs domain knowledge.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Area

Session watcher or workspace viewer

Bug description

With vscode-R 3.0.1 and its sess session connection, code I did not send is executed in my live R session. Objects defined in other files of the same project silently appear in the global environment, or overwrite objects I just created. On other occasions the whole workspace has been wiped.

The executed code never appears in the console or the R history. The same workflow in R run from Terminal.app, outside VS Code, stays clean.

I run code line by line from a single R script in a single VS Code window. Restarting R, restarting VS Code, rebooting, and using brand-new scripts did not help.

  1. An object overwritten between two consecutive commands. I fit lm1 and called emmeans() on it immediately. In between, lm1 was replaced by a different model:
> lm1 <- lmer(speakerstance ~ stance + (1 | ResponseId), data = dtl, REML = F)
> stance <- emmeans(lm1, specs = "stance")
Error in emmeans(lm1, specs = "stance") :
  No variable named stance in the reference grid
> summary(lm1)
Formula: compelling ~ reasonable + (1 | ResponseId) + (1 | scen)
   Data: dtl
 Subset: !is.na(reasonable)

The replacement matches a line in an older version of analysis.R in the same project folder, per VS Code's local file history:

lm1 <- lmer(compelling ~ reasonable + (1 | ResponseId) + (1 | scen), data = dtl, REML = F, subset = !is.na(reasonable))
  1. Objects appearing that I never created. In a fresh session, difficulty and full (both lmerModLmerTest) appeared in the workspace without my running any code that defines them.
  2. The foreign code was not sent through the terminal. It appears in neither the console nor the R history (savehistory()).
  3. The foreign model was fit in the live session, not loaded from a file.
> find("lm1")
[1] ".GlobalEnv"
> environment(formula(lm1))
<environment: R_GlobalEnv>

  1. No other startup code or hooks could explain it.
    • ~/.Rprofile only defines and attaches two ggplot theme functions.
    • There is no project .Rprofile, no .RData, and no Rprofile.site.
    • The only task callbacks are "1" (from cli::.onLoad) and "sess.workspace" (from sess::.runtime_add_task_callback).
    • No MCP or agent packages are loaded.

  2. It does not reproduce outside VS Code. The same script, packages and data, run line by line in R from Terminal.app, showed only the objects I created. ls() was clean, and emmeans() on lm1 worked as expected.

Steps to reproduce

start an R terminal with sess connected, run a script line by line, and foreign objects eventually appear.

Expected behavior

That the objects I declared remain the ones that I declared.

Environment
Component Version
R 4.5.3 (aarch64-apple-darwin20)
vscode-R 3.0.1 (with sess)
VS Code 1.142.0 (Universal)
macOS Tahoe 26.6.2
Relevant R package versions
Relevant VS Code settings
"[r]": {
  "editor.defaultFormatter": "REditorSupport.r",
},
"r.plot.useHttpgd": true,
"r.workspaceViewer.removeHiddenItems": true,
"r.sessionWatcher": true,
Logs and additional context

No response

Lenguaje dominante
TypeScript
Estrellas
1.2k
Forks
151
Merge medio
1 d 8 h
PR fusionados (30 d)
76

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de REditorSupport/vscode-R

Todos los issues de REditorSupport/vscode-R

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.