-
Notifications
You must be signed in to change notification settings - Fork 525
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
Build going into inifinite loop on running mvn oc:build -Dorg.slf4j.simpleLogger.defaultLogLevel=trace
`
#1950
Comments
Can You point me to some of resources so that I can contribute ? |
@DhirajSardar : Sorry, but this is not a good issue for newcomers. I would advise you to look into currently open issues with label |
Thank you for reaching out to me.Can you guide me to make my first
contribution ?
…On Fri, 2 Dec 2022 at 21:18, Rohan Kumar ***@***.***> wrote:
@DhirajSardar <https://github.com/DhirajSardar> : Sorry, but this is not
a good issue for newcomers. I would advise you to look into currently open
issues with label help wanted, good first issue .
—
Reply to this email directly, view it on GitHub
<#1950 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWZXMBES2MXG4VK266VKK3DWLIK6XANCNFSM6AAAAAASPIVQ6E>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@DhirajSardar : I've written a blogpost on this topic: https://rohaan.medium.com/how-to-contribute-to-eclipse-jkube-f3bc7f902bf4 . Could you please give it a read and see if it helps? |
I think there is some problem with instantiating BuildConfig during We try to upload file to OpenShift API server: but control is never returned. Checking BuildConfigOperationsImpl, it seems to be stuck waiting for response; future never seems to be getting satisfied. |
This seems to be completely related to #2000 The following snippet is evaluated when the generic trace option is enabled: Since the bodies of the request and response are printed and cannot be reset, everything else fails. We need to specifically disable tracing for that logger, or at least set the level to |
@manusa : Is it possible to disable this logger for a class (BuildConfigOperationsImpl)? |
It depends on the logger implementation, but it should be possible. In any case, I think that the logger that should be disabled is the one related to
References: |
Thanks, I just tried it and
This works as well:
|
I also tried by hardcoding HttpLoggingInterceptor's level to Should we make this change in KubernetesClient? Or shall we just add documentation/FAQ for this? |
I'm not sure I'm following here. |
…ems with KubernetesClient (eclipse-jkube#1950) Add a workaround to forcefully set `org.slf4j.simpleLogger.log.okhttp3.logging.HttpLoggingInterceptor` property to `BASIC` to prevent OkHttp's HttpLoggingInterceptor to interfere with KubernetesClient operations. Signed-off-by: Rohan Kumar <rohaan@redhat.com>
Describe the bug
When trying to use KubernetesClient verbose logs, using
org.slf4j.simpleLogger.defaultLogLevel=trace
property, I'm seeing build goes into an infinite loop in OpenShift Maven Pluginoc:build
goal. This seems to be happening during the OpenShift S2I build when BuildConfig is submitted to OpenShift APIServer.Meanwhile, the Build Pod never seems to come out of this stage:
Eclipse JKube version
1.10.0
Component
OpenShift Maven Plugin
Apache Maven version
3.8.5
Gradle version
No response
Steps to reproduce
Run
mvn oc:build -Dorg.slf4j.simpleLogger.defaultLogLevel=trace
in your project in presence of an OpenShift Cluster.Expected behavior
Build should succeed within 1-2 minutes with verbose logs
Runtime
OpenShift
Kubernetes API Server version
1.24.7
Environment
Linux
Eclipse JKube Logs
Sample Reproducer Project
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: