Fix repo discovery for private/non-existing repos #334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #333
Make sure that
audb
does not raise a backend error when looking for databases on different backends, including ones where no permissions are given or that do not exist. For the later you might argue that it is ok to raise an error, but on Artifactory we cannot differentiate between having no access rights and non-existing repos. As we usually share the same config file for all users, it seems more important to me to not fail in the case of missing access rights.The pull request first adds a test that fails for the current main branch, and changes the code afterwards to no longer raise an error.