Regressions in apps possibly related to object store backport

[PVince81]

• firewall: https://github.com/owncloud/firewall/issues/493, fix PR [stable10] Exceptions need to properly be handled in the preview plugin #31748
• user_ldap - PR Skip autocompletion tests on LDAP - they rely on a complex user and g… #31750 and backport [stable10] Skip autocompletion tests on LDAP - they rely on a complex user and g… #31751 - I wrote tests in core that were "too tricky" for the test environment in user_ldap (see details in PR). And ``user_lddap``` itself had a test scenario that was not completely setup properly to know the users and groups it could autocomplete against - fix in Tell groupMembership auto-complete test about the groups that exist user_ldap#249

[ownclouders]

GitMate.io thinks possibly related issues are #31050 ([stable10] Backport all objectstore related changes), #22058 (Primary storage - object store and encryption), #14624 (Should "object store support" be listed as an app?), #22540 (App Store shows no Apps), and #31285 (The Great Fix of object store acceptance tests ....).

[phil-davis]

user_ldap - I made the checks done by some core auto-completion acceptance tests more rigorous. I suspect that some fails of user_ldap autocomplete test scenarios are because the test scenario is not quite right, and now the test code is being tougher on the pass/fail criteria.
Looking at it...

[phil-davis]

PR #31755 and backport #31756 just make the core acceptance test code more robust, so it better survives being asked for the display name of a user that it does not know about. I noticed it because I broke it from tests in user_ldap

[PVince81]

firewall PR merged, let's wait for CI to recheck before ticking the checkbox

[PVince81]

@phil-davis can the LDAP box be ticked or is there something else we need to cover or wait for ?

[phil-davis]

I checked the box now - user_ldap CI passed this morning.

[PVince81]

firewall CI issue solved by core fix

[lock]

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.