Skip to content

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

Description

@psx95

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions