Skip to content
New issue

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

Figure out consistent strategy for error handling in resource detection #183

Open
psx95 opened this issue Nov 30, 2022 · 2 comments
Open
Labels
enhancement New feature or request priority: p3

Comments

@psx95
Copy link
Contributor

psx95 commented Nov 30, 2022

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.

@psx95 psx95 added the enhancement New feature or request label Nov 30, 2022
@aabmass
Copy link
Contributor

aabmass commented Jan 4, 2023

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.

@damemi
Copy link
Contributor

damemi commented May 8, 2023

Moving to p3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: p3
Projects
None yet
Development

No branches or pull requests

3 participants