You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're running into an issue where self update fails trying to write the tmp file in the std::env::current_exes directory. In our particular case, the std::env::current_exes directory is not writable, hence the failure. However, std::env::current_exe is writable, so it could in theory be updated.
It'd be nice if self_update could handle this case, perhaps by using /tmp if /tmp happens to be in the same filesystem as the binary being updated.
We're running into an issue where self update fails trying to write the tmp file in the
std::env::current_exe
s directory. In our particular case, thestd::env::current_exe
s directory is not writable, hence the failure. However,std::env::current_exe
is writable, so it could in theory be updated.It'd be nice if self_update could handle this case, perhaps by using
/tmp
if/tmp
happens to be in the same filesystem as the binary being updated.Related to #2
The text was updated successfully, but these errors were encountered: