auto-fix-vscode-server.description not correct type

[zeratax]

This suddenly seems to fail with:

error: A definition for option `systemd.user.services.auto-fix-vscode-server.description' is not of type `attribute set of (boolean or signed integer or string or list of (boolean or signed integer or string))'. Definition values:
       - In `/nix/store/qymv75jbxcvvwynbklna2m6kxzxkx2bh-source': "Automatically fix the VS Code server used by the remote SSH extension"
(use '--show-trace' to show detailed location information)

[msteen]

I tried in on both a server with an older version of NixOS and a VM (with release 23.05) and I could not reproduce your problem. Could you give me more details? What Nixpkgs are you using? How are you using it?

[zeratax]

I have this in my home-manager conf:

{
  imports = [
    (fetchTarball "https://github.com/msteen/nixos-vscode-server/tarball/master")
  ];

  services.vscode-server.enable = true;
  services.vscode-server.nodejsPackage = pkgs.nodejs-16_x;
}

and my system: $ nix-shell -p nix-info --run "nix-info -m":

• system: "x86_64-linux"
• host os: Linux 5.15.90.2-microsoft-standard-WSL2, NixOS, 22.11 (Raccoon), 22.11.4773.ea4c80b39be
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.11.1
• channels(root): "nixos-22.11, nixos-unstable"
• channels(nixos): "home-manager-22.11.tar.gz"
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

[msteen]

That explains the issue. You are using the NixOS module within Home Manager, and the systemd configuration for both of them differ, as an example the description attribute in your reported error is one of the differences. To solve your issue you need to import the Home Manager module instead as described in the README. The only surprising thing is that you mention it suddenly not working anymore. It should never have worked the way you had it setup. So I am curious what caused that though. Since this should solve your problem. I am closing it for now.

[zeratax]

thank you so much! idk how i overlooked that 🤦