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
fix #10822: add "local" options to omero.fs.repo.path_rules #1924
Conversation
needed for some of the path legality testing
Results from
Given the OS I assume these skips are expected. With
Should the first of these be skipped? |
Yes, |
Thanks for the clarification. I am seeing (with appropriate log tweaking) a log line confirming the current platform. However, I have only tested this PR on Mac OS, does it require wider testing? |
I'll have tested it on Linux in creating it, so I expect that we're probably okay. It's probably not worth the effort of testing the Windows side, unless perhaps the CI system is already giving us a merge-build running a Windows OMERO.server somewhere, or vbox image with one in it, in which case I could try to generate further testing suggestions. |
I'm happy for this to be merged. /cc @joshmoore |
👍 |
fix #10822: add "local" options to omero.fs.repo.path_rules
Make sure that the Blitz unit tests
FilePathRestrictionsTest
andMakePathComponentSafeTest
still pass.Try using
local required
andlocal optional
inetc/omero.properties
foromero.fs.repo.path_rules
(remember./build.py update-version
before restarting the server; you know if your changes are being taken because if you put a nonsense setting then there will be a stack trace inBlitz-0.log
). These should limit sanitization of import paths according to the machine upon which the server is running.To see the extra log message from
CurrentPlatform
you may have to adjust levels inlogback.xml
.To understand the path sanitization rules see http://www.openmicroscopy.org/site/support/omero5-staging/sysadmins/fs-upload-configuration.html#legal-file-names
Fixes https://trac.openmicroscopy.org.uk/ome/ticket/10822.
--no-rebase as FS-specific.