Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,877 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
r, typescript
Ambito
developer-experience

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
1.2k
Fork
151
Merge medio
1g 8h
PR unite (30g)
76

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di REditorSupport/vscode-R

Tutte le issue di REditorSupport/vscode-R

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.