[Ubuntu] Unclear which file is missing when "Failed to read your VS Code settings file" encountered

[denver-devacademy]

After getting to the end of setup, I noticed "Failed to read your VS Code settings file" popped up.

As far as I can tell, I have executed everything right, however I'm not entirely ruling out having just screwed something up 😛

I think it would be handy if there was some kind of check akin to the type nvm earlier that the user performs right after creating and modifying the settings.json file via VSCode to make sure everything looks right.

Also any help greatly appreciated as I'm still not too sure what I did wrong. I will probably just pull up the code for the checklist package if I can't figure it out in the next few minutes 🔍

Cheers! :)

[denver-devacademy]

Based on taking a peak into the #computer-setup channel in the Discord it seems it is for user settings, which on my machine (Pop!_OS) has been dropped at the filepath ~/.config/Code/User/settings.json

Changing settings via the UI appears to update the file and vice-versa, so going going to assume this one is alright and just an anomaly of the @donothing/checklist package :) 👍

[gerardpaapu]

Yeah, sounds like a bug in checklist.

Can you run: node -e "const os = require('os'); console.log(os.platform(), os.release())"

These are the values we use to find your settings file and it looks like yours is in the place we expect. It could be a permissions issue

[polarathene]

I am going to take a guess that the OS / uname detected was wsl? At least it looks like it would never choose linux when I looked over the script:

Likely caused by a bug in checklist source (Resolved)

const getUname = async () => {
  const short = await $('uname')
  const full = await $('uname', '-a')

  switch (short.toLowerCase()) {
    case 'linux':
      if (full.toLowerCase().indexOf('microsoft')) {
        return 'wsl'
      }

      return 'linux'

    case 'darwin':
      return 'darwin'

    default:
      throw new Error(`Sorry, I don't know what to do with uname ${short}`)
  }
}

if (full.toLowerCase().indexOf('microsoft')) would return -1 since the substring isn't present, but that will cast to true.

That would cause this step to fail:

const findVsCodeUserSettings = async () => {
  switch (await getUname()) {
    case 'darwin':
      return `${OS.homedir()}/Library/Application Support/Code/User/settings.json`

    case 'linux':
      return `${OS.homedir()}/.config/Code/User/settings.json`

    case 'wsl': {
      const APPDATA = await $('wslvar', 'APPDATA')
      const path = await $('wslpath', `${APPDATA}`)

      return `${path}/Code/User/settings.json`
    }
  }
}

Bug was fixed in EDA fork (@devacademy/checklist): #17 (comment)

[denver-devacademy]

Yeah, sounds like a bug in checklist.

Can you run: node -e "const os = require('os'); console.log(os.platform(), os.release())"

These are the values we use to find your settings file and it looks like yours is in the place we expect. It could be a permissions issue

@gerardpaapu No worries, here's the output :)

╭─denver-da@pop-os ~ 
╰─$ node -e "const os = require('os'); console.log(os.platform(), os.release())"
linux 5.18.10-76051810-generic

[polarathene]

Try npx --yes @devacademy/checklist.

[gerardpaapu]

Yeah, the computer-setup instructions need to be updated. I moved checklist from the @donothing org to the @devacademy org and then fixed that bug (or Elise did I think).

[humaid-memee]

I'm also getting the following "Failed to read your VS Code settings file" after running "npx --yes @devacademy/checklist"

I have tried to run " node -e "const os = require('os'); console.log(os.platform(), os.release())" ", and got the below output:

[gerardpaapu]

This is where we look for your settings file:

$ echo "$(wslpath $(wslvar APPDATA))/Code/User/settings.json"
/mnt/c/Users/gerard/AppData/Roaming/Code/User/settings.json

$ cat "$(wslpath $(wslvar APPDATA))/Code/User/settings.json"
{ ... }

Can you tell me if your settings file is there, and if not there, where it is? Thanks.

[gerardpaapu]

Oh, and if you're just worried about completing your setup, we know that this last check is a bit flaky on Windows so you can just get your facilitator to visually double check your settings file

[humaid-memee]

I have a settings file where you've mentioned, but another one here
C:\Users\memee\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json

Thanks Gerard, I'll check in with them in on Monday.