-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
paths.secure_write fails on CIFS volumes #172
Comments
Full exception when running Notebook:
|
Possible workaround:
|
@hroncok - I believe you've provided the missing link here! That CIFS filesystems auto-enable the execute bit. From googling, there are ways to change that behavior, but I don't think we can assume our users have access to that level of configuration, and it could potentially have adverse side affects to other applications. As a result, I think we should tolerate the execute bit on owners. @MSeal - do you see an issue with this? I would also like to clean up the comparison check to not use strings and, yes, fix up the log message to use octal (with applicable filtering through S_IMODE). I can go ahead and submit a PR and we can discuss further in that context. |
Awesome, thanks. |
Yeah execute bit doesn't matter here, just the group / public's read / write bits. I can +1 a PR for that change @kevin-bates |
Some filesystems (CIFS) auto-enable execute bits on files. As a result, we should tolerate execute on owner (but only owner). Closes: jupyter#172
@hroncok - if you'd like to take the changes for a spin on your system, that would be greatly appreciated! |
Hey, at our university Linux computers, we presumably have
/home
mounted from a CIFS storage.Jupyter Notebook Kernel fails and I've been able to reproduce the failure by this reproducer:
One thing is that the exception is a bit cryptic, in fact, it should run the 33216 number trough
oct(stat.S_IMODE(33216))
and say: Got '700' instead of '600'.The other thing is that I cannot set the mode to 600 on this FS and hence I cannot use Jupyter Notebook.
@jirutka, do you know more about the FS here?
The text was updated successfully, but these errors were encountered: