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
Some curl based healthchecks for stacks are not parsed correctly resulting in a stack trace.
A user reported a stack trace when deploying from a docker-compose.yml file.
The trace indicated that we were out of bounds on a slice reference when parsing the curl health check for the service.
I was able to repro it with the following unittest
The translateHealtcheckCurlToHTTP function does a lot of manual parsing. We should investigate using url.Parse and other methods for doing some of the parsing while addressing the issue.
The text was updated successfully, but these errors were encountered:
There was at least one issue parsing for the url to transform the stack health check
to the data needed for a health check in kubernetes. The issue discovered was
an out of bounds on a slice issue when there was no path present.
This commit fixes#1974
Signed-off-by: Jacob MacElroy <jacob@okteto.com>
* Simplify curl-based healthcheck parsing for stacks.
There was at least one issue parsing for the url to transform the stack health check
to the data needed for a health check in kubernetes. The issue discovered was
an out of bounds on a slice issue when there was no path present.
This commit fixes#1974
Signed-off-by: Jacob MacElroy <jacob@okteto.com>
* Removing leftover print statements.
Some
curl
based healthchecks for stacks are not parsed correctly resulting in a stack trace.A user reported a stack trace when deploying from a docker-compose.yml file.
The trace indicated that we were out of bounds on a slice reference when parsing the curl health check for the service.
I was able to repro it with the following unittest
This test results in a stack of
The user was on okteto CLI 1.14.5
Their check did not repro for me and was like this but it seems to be similar to the test based on the stack
The
translateHealtcheckCurlToHTTP
function does a lot of manual parsing. We should investigate usingurl.Parse
and other methods for doing some of the parsing while addressing the issue.The text was updated successfully, but these errors were encountered: