We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There needs to be a consistent strategy to follow error handling within the resource detection code in case the code reaches unexpected conditions.
As of now, all exceptions & unexpected conditions are either swallowed or simply ignored.
The text was updated successfully, but these errors were encountered:
From @dashpole: sometimes we log errors + swallow and sometimes throw exceptions. Would be nice to come up with a strategy here before working on it.
Sorry, something went wrong.
Moving to p3
No branches or pull requests
There needs to be a consistent strategy to follow error handling within the resource detection code in case the code reaches unexpected conditions.
As of now, all exceptions & unexpected conditions are either swallowed or simply ignored.
The text was updated successfully, but these errors were encountered: