Voltra
You're literally the embodiment of that XKCD and we didn't even know... Thank you for all your hard work on core-js, you've carried the whole modern Era of the web...
Here's the entire stack trace straight out of the Admin>Logging ``` {"reqId":"XXXXX","level":3,"time":"XXXXX","remoteAddr":"XXXXX","user":"XXXXX","app":"webdav","method":"PROPFIND","url":"/remote.php/webdav","message":"The view passed to the node should not have any fake root set","userAgent":"XXXXX","version":"25.0.7.1","exception":{"Exception":"OCP\\PreConditionNotMetException","Message":"The view passed to the node should...
I've updated the initial issue message with the missing information that could be retrieved
Gotcha, updated for your convenience
Here's the log that I get using that patch (which surprisingly seems to have a bit more details): ```json { "reqId": "XXXXX", "level": 3, "time": "XXXXX", "remoteAddr": "XXXXX", "user": "MY_USER",...
Message from the constructor: ```json { "reqId": "XXXXX", "level": 3, "time": "XXXXX", "remoteAddr": "XXXXX", "user": "MY_USER", "app": "no app in context", "method": "PROPFIND", "url": "/remote.php/dav/files/MY_USER/", "message": "new View: ", "userAgent":...
There are a handful, but they're all the same messages: `new View: ` or `View service requested: `
Upgrading to 26.0.2 seems to fix the issue as well
See #11450
That is quite possible since my test use case seemingly only use `hydrated` hooks. I'll check it out and adjust