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

`sess` package progress

Fermée
  • Quelque chose ne va pas ?
#1,712 6 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
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Calme
Stack technique
r, vscode
Domaine
developer-experience, tooling

Piste de recherche

Commencez par reproduire l’échec avec sess::connect() et la commande rv add indiquée, en utilisant le lanceur .vscode/arf et les paramètres VS Code fournis. Comparez les environnements de projet fonctionnels et défaillants, notamment le commit de sess et l’avertissement connection-info. C’est terminé lorsque sess se connecte correctement depuis le terminal R et que l’avertissement indiqué ne se produit plus.

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

Description

bug

Describe the bug
Early adopter of sess here just adding to the data in case its useful! I have one or two projects for which sess installed from the VSCode popup prompt, and it worked perfectly, and others for which it didn't. Today, I tried to deliberately add sess using rv add (I use rv for project package management):

rv repositories active!
repositories: 
  CRAN: https://packagemanager.posit.co/cran/latest

rv libpaths active!
library paths: 
  /n/holylabs/cgolden_lab/Lab/frontier/works/prospectors/prospectorKiribatiBioMarkers/rv/library/4.5/x86_64/redhat8
  /n/home03/ttapera/software/spack/opt/spack/linux-icelake/r-4.5.1-7hho5emqpuvlwt7hhy7i5fval54zz7mx/rlib/R/library
Warning message:
In sess::connect(use_rstudioapi = as.logical(Sys.getenv("SESS_RSTUDIOAPI",  :
  [sess] Connection info not available. Cannot connect to VS Code.
# arf console v0.3.3
# Edit mode: emacs
# R 4.5.1 is ready.
# Type :cmds for meta commands list, Ctrl+D to exit.
R 4.5.1> sess::connect()
Warning message:
In sess::connect() :
  [sess] Connection info not available. Cannot connect to VS Code.
R 4.5.1> sessionInfo()
R version 4.5.1 (2025-06-13)
Platform: x86_64-pc-linux-gnu
Running under: Rocky Linux 8.10 (Green Obsidian)

Matrix products: default
BLAS/LAPACK: /n/home03/ttapera/software/spack/opt/spack/linux-icelake/openblas-0.3.33-xlojbage3rtl5frqwshts2o3qlkej7t6/lib/libopenblas-r0.3.33.so;  LAPACK version 3.12.0

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8     LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8    LC_PAPER=en_US.UTF-8      
 [8] LC_NAME=C                  LC_ADDRESS=C               LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       

time zone: America/New_York
tzcode source: internal

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

loaded via a namespace (and not attached):
[1] compiler_4.5.1 sess_3.0.0    
R 4.5.1>

To Reproduce
Steps to reproduce the behavior:

rv add sess --git https://github.com/REditorSupport/vscode-R --directory sess --commit 20f32fe142145152c4cfa6a65f9a89 4f77adde9e

Can you fix this issue by yourself? (We appreciate the help)

Yes / No

(If yes,) can we assist you with anything?

(If applicable) Please attach setting.json

{
    "r.plot.useHttpgd": true,
    "r.rterm.linux": "${workspaceFolder}/.vscode/arf",
    "r.workspaceViewer.showObjectSize": true,
    "terminal.integrated.defaultProfile.linux": "bash",
    "terminal.integrated.profiles.linux": {
        "bash": {
        "path": "/bin/bash"
        }
    },
    "livePreview.defaultPreviewPath": "/docs/index.html",
    "r.bracketedPaste": true,
    "r.sessionWatcher": true,
    "r.alwaysUseActiveTerminal": true,
    "r.rpath.linux": "/n/holylabs/cgolden_lab/Lab/frontier/works/prospectors/prospectorKiribatiBioMarkers/.spack-env/view/bin/R",
    "python.terminal.activateEnvInCurrentTerminal": true,
    "r.libPaths": [
        "/n/holylabs/cgolden_lab/Lab/frontier/works/prospectors/prospectorKiribatiBioMarkers/rv/library/4.5/x86_64/redhat8",
        "/n/home03/ttapera/software/spack/opt/spack/linux-icelake/r-4.5.1-7hho5emqpuvlwt7hhy7i5fval54zz7mx/rlib/R/library"
    ]
}

# ./.vscode/arf
#!/usr/bin/env bash
set -euo pipefail

PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"

SPACK_VIEW="$PROJECT_ROOT/.spack-env/view"

export PATH="$SPACK_VIEW/bin:$PATH"

export LD_LIBRARY_PATH="$SPACK_VIEW/lib:$SPACK_VIEW/lib64:${LD_LIBRARY_PATH:-}"

export PKG_CONFIG_PATH="$SPACK_VIEW/lib/pkgconfig:$SPACK_VIEW/lib64/pkgconfig:${PKG_CONFIG_PATH:-}"

exec  ~/.cargo/bin/arf "$@"

Expected behavior
sess connected or sess::connect() to be successful
Screenshots
If applicable, add screenshots to help explain your problem.
You can show the keyboard contents by pressing F1 and Developer: toggle screencast mode

Environment (please complete the following information):

  • OS: Linux (HPC Rocky cluster)
  • VSCode Version: 1.122.1 (Universal)
  • R Version: 4.5.1
  • vscode-R version: 3.0.0-rc.0

Additional context
Good luck! I'm quite optimistic that the sess package is the solution we've all been waiting for

Langage dominant
TypeScript
Étoiles
1.2k
Forks
139
Merge moyen
19 h 46 min
PR mergées (30 j)
26

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.