You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "astefanutti (via GitHub)" <gi...@apache.org> on 2023/05/09 10:11:25 UTC

[GitHub] [camel-k] astefanutti commented on pull request #4300: fix(operator): do not panic if cannot set GOMAXPROCS

astefanutti commented on PR #4300:
URL: https://github.com/apache/camel-k/pull/4300#issuecomment-1539854866

   > @astefanutti I'd like your opinion on this one. I have the feeling we should be safe by just logging the error (then it will be up to the operator installer to figure it out how to solve this problem to improve concurrency). In this way we at least let the operator run in situations where we cannot control the cluster (ie, the github actions which suddenly stopped to work).
   
   @squakez sorry for the late reply, this felt under my radar. Error logging looks like a pragmatic approach. I think situations where this could lead to nasty issues are very seldom. This would ideally go away anyway with golang/go#33803.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org