Condition is detected and handled (logged, ignored).
An unexpected condition is met and a non-existent variable is accessed.
Ref https://sentry.rullzer.com/sentry/nextcloud/issues/150 (for people with access).
GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/4730 (Storage), https://github.com/nextcloud/server/issues/10665 (DAV Error in Nextcloud 14), https://github.com/nextcloud/server/pull/10417 (Fix undefined constant error for STATUS_SERVICE_UNAVAILABLE), https://github.com/nextcloud/server/issues/5684 (Error Message "undefined offset" with comments), and https://github.com/nextcloud/server/issues/9784 (Undefined index: {DAV:}getlastmodified at /var/www/html/lib/private/Files/Storage/DAV.php#582).
@nextcloud-bot nope, not even close …
Still relevant @ChristophWurst ?
Yes. See https://github.com/nextcloud/server/issues/16471 for example. We should not reach return $response if undefined.
Nice!
So duplicate or relevant of #16471 @kesselb ?
Relevant but not a duplicate. #16471 is running into the undefined return but the problem is with sabre/dav or alfresco. This issue is about the incomplete error handling.