Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hello yaml example output #3124

Closed
lucamaf opened this issue Mar 16, 2022 · 5 comments
Closed

hello yaml example output #3124

lucamaf opened this issue Mar 16, 2022 · 5 comments
Labels
kind/question Further information is requested status/stale

Comments

@lucamaf
Copy link

lucamaf commented Mar 16, 2022

I just tried the hello yaml example and I'm pretty sure we are not supposed to output this for every hello line in the container log:

�[39m�[38;5;145m2022-03-16 18:03:54,035�[39m�[38;5;188m �[39m�[38;5;107mINFO �[39m�[38;5;188m [�[39m�[38;5;69minfo�[39m�[38;5;188m] (�[39m�[38;5;71mCamel (camel-1) thread #0 - timer://yaml�[39m�[38;5;188m) �[39m�[38;5;151mExchange[ExchangePattern: InOnly, BodyType: String, Body: Hello Camel K from yaml]�[39m�[38;5;203m�[39m�[38;5;227m

I'm running camelk installed through operator (version 1.6.3) over OpenShift 4.9

@tadayosi
Copy link
Member

Have you tested it with the latest Camel K release? I checked it with 1.9.0-SNAPSHOT and it seems to be fixed already.

@squakez
Copy link
Contributor

squakez commented Mar 17, 2022

@lucamaf is that the output coming from HTML Pod log panel? or is it coming from the CLI (ie, kamel log xyz)?

@squakez squakez added the kind/question Further information is requested label Mar 17, 2022
@lucamaf
Copy link
Author

lucamaf commented Mar 17, 2022

it is coming from the Pod log panel, the kamel log command output looks good

@squakez
Copy link
Contributor

squakez commented Mar 17, 2022

Then, it is likely some error in the way openshift show certain characters. I don't think we can do much about that :(

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested status/stale
Projects
None yet
Development

No branches or pull requests

3 participants