infinite symlink: /tmp/devenv-XXX/devenv-XXX -> /tmp/devenv-XXX

[bobvanderlinden]

Describe the bug Currently it seems that any devenv creates a devenv-XXX directory in /tmp and creates a symlink in there that points to the same directory.

$ ls -l /tmp/devenv-*/
/tmp/devenv-f4c9edc/:
total 0
lrwxrwxrwx 1 bob.vanderlinden users 19 Apr  5 00:03 devenv-f4c9edc -> /tmp/devenv-f4c9edc

Tools like vite will run into errors when recursing into these directories:

Error: ELOOP: too many symbolic links encountered, stat '.../.devenv/run/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1/devenv-4b8b6c1

Are these symlinks cause of a bug or are they intentionally created?

To reproduce

From what I can tell, these symlinks are created for all devenvs (there are tons of /tmp/devenv-* and all consistently have the symlink).

I ran this in a project using:

{
  languages.javascript.enable = true;
}

And which also uses vite.

Version

devenv 1.0.2 (x86_64-linux)

[domenkozar]

I'm looking into this, but can't see what's creating the symlink.

[domenkozar]

      ls ${lib.escapeShellArg config.devenv.runtime} || true
      mkdir -p ${lib.escapeShellArg config.devenv.runtime}
      ls ${lib.escapeShellArg config.devenv.runtime}

prints

ls: cannot access '/run/user/1000/devenv-0fcf29a': No such file or directory
devenv-0fcf29a

[domenkozar]

++++ mkdir -p /run/user/1000/devenv-0fcf29a
++++ ls /run/user/1000/devenv-0fcf29a
devenv-0fcf29a