Sprint5 server bugs#369
Conversation
Data that was 1) in the system group and 2) queried via omero.group=-1 was causing an internal exception. The short-circuit block at the top of allowLoad was failing to cache permissions for core groups.
Neither of these types will have a group so short-circuiting the if/else will prevent a WARN statement.
|
All the fixes surrounding #9632 seem to be working nicely. The last two commits (2482a7f, 3cc848b) were not in the build today, right @joshmoore? |
|
@chris-allan, correct. Adding comment to description now. |
|
@joshmoore, @chris-allan: Will check difference between both clients |
|
@chris-allan, @joshmoore: tested in both clients with various permissions level and user's roles. No problem noticed now. Updating testing setup sheet |
|
@joshmoore, @chris-allan: found a problem
|
|
@joshmoore: similar problem in web
Problem seems only to be for read-write, read-annotate seems fine. |
|
Do you mean "read-write-1"? It's currently listed as rwra: |
|
(and user-5 is only a member, not an owner of that group) |
|
@joshmoore: that will explain, another problem in the setup script. It should be |
|
@joshmoore: doc updated ome/omero-documentation#92 |
|
@joshmoore: I have set correctly the permissions of read-write. Now it works as expected. |
These are issues found during the last round of testing of the server.