This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Regular expressions in port detection might panic #220
Labels
kind/bug
Something isn't working
Comments
Target Date: 28 June 2023 FYI Just started working on the issue :) |
Thanks for the heads-up, @thepetk ! |
2 tasks
I've created a PR to replace |
@rm3l the pr is now merged. I've also put a test for this case in order to ensure that we are always covering this. |
This was referenced Jun 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which area this feature is related to?
/kind bug
What versions of software are you using?
Go project
Operating System and version:
Fedora 38
Go Pkg Version:
We are currently using Alizer on a1115da, but I locally tested by using the latest commit (59b155e), and the issue still persists.
Bug Summary
Describe the bug:
Tried to run
odo analyze
against https://github.com/backstage/backstage.odo analyze
is basically a wrapper around Alizer for Devfile, port and component name detection.To Reproduce:
Expected behavior
Not panicking, but returning an appropriate error to the caller, so they can handle it.
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
Additional context
Observed in the following issues:
odo dev
freezes then panics when run from~
odo#6780Any workaround?
—
Suggestion on how to fix the bug
We guessed Alizer should take care with
regexp.MustCompile
when the regular expression is dynamic.The text was updated successfully, but these errors were encountered: