Skip to content

Polyglot Notebook unable to load R kernel in new working folders #3864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 of 17 tasks
WttBe opened this issue Feb 24, 2025 · 2 comments
Open
3 of 17 tasks

Polyglot Notebook unable to load R kernel in new working folders #3864

WttBe opened this issue Feb 24, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@WttBe
Copy link

WttBe commented Feb 24, 2025

Describe the bug

Since the last update, I encounter a strange bug while trying to load Python and R kernels (see below for code lines):

  • In my old working folders, both kernels load without any issue
  • In new working folders, Python loads while R kernel's loading runs in a loop
  • If I relocate new files into old working folders, loading is working properly, but if I relocate old files into new working folders, loading fails.

#!connect jupyter --kernel-name pythonkernel --kernel-spec python3
#!connect jupyter --kernel-name Rkernel --kernel-spec ir

Please complete the following:

Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

Version: 1.0.611902

  • OS
    • Windows 11
    • Windows 10
    • macOS
    • Linux (Please specify distro)
    • iOS
    • Android
  • Browser
    • Chrome
    • Edge
    • Firefox
    • Safari
  • Frontend
    • Jupyter Notebook
    • Jupyter Lab
    • nteract
    • Visual Studio Code
    • Visual Studio Code Insiders
    • Visual Studio
    • Other (please specify)

Screenshots

If applicable, add screenshots to help explain your problem.

@jonsequitur
Copy link
Contributor

Could you provide some logs? You can enable logging by editing the Polyglot Notebooks extension's settings for Kernel Transport Args and adding the following:

"dotnet-interactive.kernelTransportArgs": [
    "{dotnet_path}",
    "tool",
    "run",
    "dotnet-interactive",
    "--",
    "[vscode]",
    "stdio",
    "--working-dir",
    "{working_dir}",
+   "--log-path",
+   "c:\\temp\\your-log-folder-name",
+   "--verbose",
],

Image

@jonsequitur jonsequitur added bug Something isn't working waiting-on-feedback labels Feb 24, 2025
@WttBe
Copy link
Author

WttBe commented Feb 24, 2025

Here they are! Thanks for your rapid answer!

Log New Folder.log

Log Old Folder.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants