RIO.Process is running an "original" instead of a symbolic link about rio HOT 7 CLOSED

What happens if you give it an absolute path in the first place?

from rio.

@snoyberg all right, I've created a minimal self-containing repo. I also confirm that the code works on macOS, but not Ubuntu 20.04, and suspect it might work fine on Ubuntu 18.04, which might be somewhat alarming https://github.com/k-bx/rio-process-symlink-issue

The README captures the build and run instructions

from rio.

Does this reproduce with the process package?

from rio.

Yes, I rewrote it using the UnliftIO.Process and it works now

from rio.

I'm quite confused about the claim that this works on macOS and Ubuntu 18.04 but not Ubuntu 20.04. I think I know what the problem is: usage of canonicalizePath instead of makeAbsolute in findExecutable. However, that functions behaves identically on macOS and Ubuntu 18.04: resolving symbolic links.

The repro you've provided isn't really minimal, since it depends on assumptions of virtualenv working identically across all OSes and versions. I'm fairly certain that's the problem here. My recommendation: can you try replacing canonicalizePath with makeAbsolute in the codebase and see if that solves the problem you're seeing?

from rio.

I don't see a downside to the change, so I've opened #218.

from rio.

@snoyberg yes, tested with the patched rio, it works now. Thank you!

from rio.