Skip to content

Alizer component detection never ends for specific projects #1279

@thepetk

Description

@thepetk

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area alizer

Bug Summary

Describe the bug:

Upon component detection alizer never ends its detection process and the user is waiting forever. The two projects that this was experienced are:

To Reproduce:

Clone one of the above repos locally and try to run alizer against them using the component command:

make build
./alizer component ~/rhsm-subscriptions

Expected behavior

Alizer should be able to detect all components inside those projects or in case there is none to exit normally.

Additional context

N/A

Any workaround?

N/A

Metadata

Metadata

Assignees

Labels

area/alizerEnhancement or issue related to the alizer repokind/bugSomething isn't working

Type

No type

Projects

Status

Done ✅

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions