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
test suite failures due to lack of xdmp:get-server-field privilege #778
Comments
Why should rest-writer be assigned a xdmp:get-server-field? Isn't that a bug, then? Or is this issue missing parts of user setup / other configurations? |
looks like a regression/bug to me. accessing the rest error format should be amped. rest-writer should not have any privileges beyond the rest-writer and rest-reader privileges. |
There are a lot of errors in REST API unit tests today. Looking into it. |
I see some notices that the nightly build was failing on mac and window last night. Maybe this issue will be resolved underneath. |
@tdiepenbrock can you confirm that you didn't get any error when you ran |
I ask because I don't know how to duplicate this. When I follow the same steps I don't see the same errors |
Sorry, let me acknowledge that I haven't yet tried to fully duplicate your env. I'd just be very surprised if this is env related . . . plus I don't have easy access to MacOS. |
Running the test suite from the develop branch yields 5 failures/132 errors. Many of these errors are due to the request user not having the xdmp:get-server-field privilege. Log is attached.
Tests were run in the following environment:
ML version: 9.0-1.1
OS: MacOS.
Java version: 1.8.0_102-b14.
Client API: develop branch at bdbfa6d.
Maven: Apache Maven 3.5.0
This was a brand new installation of everything except Java: I had freshly installed Maven for the first time, ML was a bare install of 9.0-1.1, and I had newly cloned the develop branch. I ran mvn test-compile, followed by mvn exec:java@test-server-init, followed by mvn test..
When I gave the rest-writer role the xdmp:get-server-field privilege, most of the errors went away and I was left with errors that Sam Mefford was also getting, plus five semantics-related errors.
java-client-api-develop-failures.txt
The text was updated successfully, but these errors were encountered: