-
Notifications
You must be signed in to change notification settings - Fork 72
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
New exception message is confusing #210
Comments
Sravan, can you help me understand what's happening here? The inline comments don't clarify it for me. It looks like you're writing a valid module. Yet the method name implies to me these are negative tests. Are these? If so, why do they fail? I need to translate this into REST language to send this error on to the lower layers. |
This an existing test in regression which started failing because of exception message mismatch, I have not tried in understanding the test but I see the message it is spitting now is confusing, here is the complete test for your reference |
The error changed in lower layers, so I need to create an issue for them. Can you provide a wire trace? That should help the most. |
@srinathgit can you verify that this test is no longer failing? I'm guessing this issue has just lingerred unnecessarily. |
Assigning the case to @georgeajit |
@sammefford The same (confusing) exception is still being thrown "Local message: Could not write resource at /foo/my/path/to/my/module.xqy. Server Message: Request failed. Error body not received from server". But the test has been changed as below and so it passess
|
Ok, you'll need to update that test. See the unit test I added. ExtensionLibrariesManager will now throw an IllegalStateException with the message "libraryPath (the modules database path under which you install an asset) must begin with /ext/". Let me know if you feel that message is still confusing. |
The test has been modified with new exception message |
Regression test TestCRUDModulesDb is failing in nightly regression
The text was updated successfully, but these errors were encountered: