-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
OC10: regression with custom sharing provider #27617
Comments
CSRF check failed? Sometimes that message happens due to infinite recursions. Can you debug the the code and provide more info ? So far that's not enough info to be able to provide help. |
another option is bisecting to find out what commit broke it |
closing, not enough info. |
Hello, we don't have time now for debugging these kind of regressions. Please leave the issue open so we do not forget about it. |
@PVince81: how do you actually test "pluggability" with your interfaces such as sharing.managerFactory? You must surely have a simple mockup class for testing which proves that something else than a default, legacy implementation can be plugged in? We have seen before (#26607) that your system is not properly separated into independent components and you have implicit dependencies which violate the interfaces. |
As far as I know there are currently no proper tests for pluggability. Ideal would probably be to have a test instance with a custom sharing manager / storage implementations that runs in a separate test suite. Most of the refactored Sharing v2 components should already be decoupled as much as possible. The remaining code that was discovered is from Sharing v1 and is mostly unused. Needs clean up. Note that Sharing and FS need to be implemented together, these two components cannot be separated. This means that the current sharing code can use filecache and if someone reimplements the filecache logic they also need to reimplement that matching sharing part. |
Hey, this issue has been closed because the label |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When using our custom sharing manager factory:
ownCloud returns 500 error with following log line message:
The text was updated successfully, but these errors were encountered: