squakez closed issue #5161: Debug Integrations failing
URL: https://github.com/apache/camel-k/issues/5161
--
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
gansheer commented on issue #5161:
URL: https://github.com/apache/camel-k/issues/5161#issuecomment-1956680842
That could explain something I think I saw in some tests I saw : an
integration pod created twice with the first one gone in the blink of an eyes
(well more my terminal refresh).
squakez commented on issue #5161:
URL: https://github.com/apache/camel-k/issues/5161#issuecomment-1956540607
I think the problem may have been caused by the introduction of
`.status.trait`. Whenever there is an update on the Integration, for some
reason we are updating it twice. See the Pod
gansheer commented on issue #5161:
URL: https://github.com/apache/camel-k/issues/5161#issuecomment-1948800341
No problem, I will check.
--
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 specifi
squakez commented on issue #5161:
URL: https://github.com/apache/camel-k/issues/5161#issuecomment-1948386801
I think it may be related to the JVM trait changes we've applied lately.
@gansheer do you mind having a look?
--
This is an automated message from the Apache Git Service.
To respon
squakez opened a new issue, #5161:
URL: https://github.com/apache/camel-k/issues/5161
### What happened?
❌ TestKamelCLIDebug (9m49.89s)
❌ TestKamelCLIDebug/debug_local_default_port_check (9m42.16s)
### Steps to reproduce
_No response_
### Relevant log output
