Xonsh plumbing problem

Technical Support
, ,
1

Hi.

My dev environment is a Ubuntu virtual machine and every now and again the links for xonsh get updated and I get this message. This is the reason I have a virtual machine with snap shots and not WSL.

[05-29 07:12:16.201] Debug id_rsa OK
[05-29 07:12:16.201] ERROR :: Errors during the initialization of Torizon IDE Extension.
[05-29 07:12:16.201] HOUSTON WE HAVE A PROBLEM!
[05-29 07:12:16.201] PLEASE READ THE LOGS!
[05-29 07:12:16.202] ERROR :: Please share this log on https://community.toradex.com

Which logs should I read, I am not experienced in extension development and was wondering where they were or how to investigate the extension to find them.

I have discovered that:

[05-29 07:12:03.680] Warning: /usr/bin/xonsh is not linked to $HOME/.local/bin/xonsh

$ ls -al /usr/bin/xonsh 
lrwxrwxrwx 1 root root 66 Apr 29 08:16 /usr/bin/xonsh -> /home/lloydj/snap/code/230/.local/share/pipx/venvs/xonsh/bin/xonsh

and not to

$ ls -al ~/.local/bin/xonsh
lrwxrwxrwx 1 lloydj lloydj 66 May 28 09:01 /home/lloydj/.local/bin/xonsh -> /home/lloydj/snap/code/234/.local/share/pipx/venvs/xonsh/bin/xonsh

So it looks like my local links get updated to 234 when xonsh gets upgraded but the usr/bin links do not and point directly to the old install 230 and not via my local links.

I am still able to build the containers so this is just an error message that messes with my brain at start up.

Lloyd

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Torizon IDE Extension Logs Location

To investigate the initialization errors you’re seeing, you can access the VS Code internal logs through the Developer Tools (1):

  1. Open the VS Code command palette (Ctrl+Shift+P)
  2. Select Developer: Toggle Developer Tools (1)
  3. In the new window, click on the Console tab to check the logs (1)

This will show you detailed error messages and stack traces that can help identify the root cause of the initialization issue (1).

Xonsh Link Issue Analysis

The warning about xonsh links appears to be related to your snap-based VS Code installation where the extension expects xonsh to be linked to $HOME/.local/bin/xonsh, but your system has it linked via /usr/bin/xonsh to an older snap version (230 vs 234).

Since you mentioned you can still build containers successfully, this appears to be a non-critical warning that occurs during extension initialization. The extension likely performs environment checks during startup and flags this inconsistency.

Additional Troubleshooting Steps

You can also check the Terminal tab in VS Code for additional error message logs, and look for any tasks marked in red color in the terminal entries, which should give hints about what specifically failed during initialization (1).

If the issue persists and affects functionality beyond the startup warning, you may want to ensure your VS Code and the Torizon IDE Extension are both updated to their latest versions.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hello @Lloyd,

Here the full logs from the same window would be useful.
However, from your further comments the problem is clear.

Checking with the IDE Extension team, the issue you see is related to the use of VSCode installed via a snap.
This configuration is not supported and could lead to unexpected issues.

Our recommendation is to install VSCode via the .deb.

Best Regards,
Bruno