You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When requesting a non-existent version on a stack, such as GET /devfiles/java-maven/not-exist, will cause an uncaught panic error due to accessing error entity which is set to nil when responding with 404 Not Found. This is believed to be a mistake in writing the response.
To Reproduce:
Replace $REGISTRY_HOST with hostname and port which the registry server is listening on, NOT RECOMMENDED to try on production deployments.
/kind bug
Which area this bug is related to?
/area registry
What versions of software are you using?
Operating System: Linux
Go Pkg Version: 1.17
Bug Summary
Describe the bug:
When requesting a non-existent version on a stack, such as
GET /devfiles/java-maven/not-exist
, will cause an uncaught panic error due to accessing error entity which is set tonil
when responding with404 Not Found
. This is believed to be a mistake in writing the response.To Reproduce:
Replace
$REGISTRY_HOST
with hostname and port which the registry server is listening on, NOT RECOMMENDED to try on production deployments.curl -L https://$REGISTRY_HOST/devfiles/java-maven/non-exist
Expected behavior
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.
From testing:
Additional context
Any workaround?
N/A
Suggestion on how to fix the bug
Remove /index/server/pkg/server/endpoint.go#L536
Target Date: 07-29-2022
The text was updated successfully, but these errors were encountered: