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
I'm using mlxu (0.1.10) and noticed that it creates temporary files under /tmp/mlxu. The problem with the current framework is that, if multiple people are using the system and running experiments using mlxu, the mlxu folder in temp in /tmp/ is created with write permissions only for whoever first created the folder. Is there a way to get around this? Perhaps by setting an environment variable that puts those folders elsewhere?
I would suggest in the future making the temp folder /tmp/mlxu_<uid>/ for example to avoid this problem.
The text was updated successfully, but these errors were encountered:
I still think that it would be good to set the default directory to something a bit more general and robust (#3). Also, it shouldn't break any properly written code because one would either be relying on whatever the default directory is or setting it explicitly. Can you think of a reason not to implement that change?
This issue has been open for a while. If you disagree or don't want to apply this change for whatever reason, I understand. Even in that case, please close this issue and the associated PR to mark it one way or the other.
I'm using
mlxu
(0.1.10) and noticed that it creates temporary files under/tmp/mlxu
. The problem with the current framework is that, if multiple people are using the system and running experiments usingmlxu
, themlxu
folder in temp in/tmp/
is created with write permissions only for whoever first created the folder. Is there a way to get around this? Perhaps by setting an environment variable that puts those folders elsewhere?I would suggest in the future making the temp folder
/tmp/mlxu_<uid>/
for example to avoid this problem.The text was updated successfully, but these errors were encountered: