Configure Path no longer updating .bashrc/.zshrc/.bash_profile when option set to automatic about rancher-desktop HOT 6 OPEN

Hi! Sorry, we changed the code around there to reduce the chance of files being accidentally clobbered, and it's possible that I made some errors.

Could you enabled debug logging, restart Rancher Desktop (to ensure the relevant code runs), and then upload your logs? The most relevant file is probably integrations.log but some of the other ones are possibly useful too.

from rancher-desktop.

@mook-as sure - If it can help the background.log file shows an entry about the change that was made to avoid touching files with xattr

2024-08-07T16:46:12.828Z: UnhandledRejectionWarning: Error: Refusing to manage /Users/lballerini/.bash_profile which has extended attributes

Earlier today I tried to rollback to v1.14.2 and the option works fine

integrations.log
background.log

from rancher-desktop.

Ah, yeah, that means we're intentionally avoiding to change it (because we now create a new file and rename it in-place, which would have lost your extended attributes).

Can you do a xattr -lv /Users/lballerini/.bash_profile to see what extended attributes the file has? I'm not expecting any, but it obviously has something.

from rancher-desktop.

Only one, com.apple.provenance same also on the .zshrc and .bashrc

from rancher-desktop.

Another indirect consequence, is that the Diagnostics section shows an error if the path is exported only on one file. I use zsh so only adding to the .zshrc file, produced this alert

The ~/.rd/bin directory has not been added to the PATH, so command-line utilities are not configured in your bash shell.

from rancher-desktop.

Yeah, the full set of diagnostics isn't there yet; see #7297 for some of that.

It looks like com.apple.provenance (per this) has to do with quarantine and is probably safe to remove, so we might want to consider just allowing the write if that's the only xattr involved.

from rancher-desktop.