bfitzpat commented on issue #889: Camel-K operator should clean up kits and kit
builders after integrations are deleted
URL: https://github.com/apache/camel-k/issues/889#issuecomment-532229927
Running `kamel reset` does help clean up the errant artifacts, so that's a
good workaround in
bfitzpat commented on issue #938: Kamel cli should send exit code when
integration in --dev mode is deleted
URL: https://github.com/apache/camel-k/issues/938#issuecomment-532211446
I have tried sending a kill signal to the running process and neither SIGINT
nor SIGKILL seems to do any
astefanutti commented on issue #935: fix(knative): Use channel hostname to
filter Knative history header
URL: https://github.com/apache/camel-k/pull/935#issuecomment-532153915
Yes, I've actually faced the issue while running some examples on a live
cluster and I can confirm the history
astefanutti commented on a change in pull request #922: fix: Add option to
disable Kaniko cache warming
URL: https://github.com/apache/camel-k/pull/922#discussion_r325053732
##
File path: pkg/controller/integrationplatform/initialize.go
##
@@ -137,7 +137,7 @@ func (action
asifdxtreme commented on a change in pull request #922: fix: Add option to
disable Kaniko cache warming
URL: https://github.com/apache/camel-k/pull/922#discussion_r324988292
##
File path: pkg/controller/integrationplatform/initialize.go
##
@@ -137,7 +137,7 @@ func (action
bfitzpat opened a new issue #938: Kamel cli should send exit code when
integration in --dev mode is deleted
URL: https://github.com/apache/camel-k/issues/938
In the tooling I'm having some difficulty finding ways to kill a --dev mode
integration effectively.
Essentially we're
asf-ci commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-531906838
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/162/Build result:
FAILURE[...truncated
ffang commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-531879690
@zhfeng , thanks for the info, I will take a close look.
This is an automated message from the Apache Git
ffang commented on a change in pull request #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#discussion_r324798270
##
File path:
integration-tests/jira/src/main/java/org/apache/camel/quarkus/component/jira/it/JiraResource.java
##
@@ -0,0 +1,88 @@
+/*
ffang commented on a change in pull request #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#discussion_r324798127
##
File path: extensions/jira/deployment/pom.xml
##
@@ -0,0 +1,57 @@
+
Review comment:
@WillemJiang , Apache License header added,
ppalaga commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531850873
A simple `vertx-web` itest hangs also on plain Quarkus, but only in 0.22.0
branch. It works on the master. I filed
oscerd merged pull request #202: Upgrade to Quarkus 0.22.0
URL: https://github.com/apache/camel-quarkus/pull/202
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
asf-ci commented on issue #202: Upgrade to Quarkus 0.22.0
URL: https://github.com/apache/camel-quarkus/pull/202#issuecomment-531821533
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/161/
zhfeng commented on issue #143: Create a Camel AMQP extension
URL: https://github.com/apache/camel-quarkus/issues/143#issuecomment-531808348
we have to wait for the https://github.com/quarkusio/quarkus/issues/3436
This is an
ppalaga opened a new pull request #202: Upgrade to Quarkus 0.22.0
URL: https://github.com/apache/camel-quarkus/pull/202
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
zhfeng commented on issue #143: Create a Camel AMQP extension
URL: https://github.com/apache/camel-quarkus/issues/143#issuecomment-531784317
https://github.com/quarkusio/quarkus/pull/4044
This is an automated message from the
zhfeng commented on issue #143: Create a Camel AMQP extension
URL: https://github.com/apache/camel-quarkus/issues/143#issuecomment-531782828
The camel-amqp 3.0.0-RC1 has org.springframework:spring-context version
5.1.9.RELEASE but the io.quarkus:quarkus-bom 0.21.2 has 5.1.8.RELEASE.
zregvart merged pull request #88: CAMEL-13818: design of the blog section
URL: https://github.com/apache/camel-website/pull/88
This is an automated message from the Apache Git Service.
To respond to the message, please log
zregvart merged pull request #89: CAMEL-13889: website - Tab title should be
just Apache Camel
URL: https://github.com/apache/camel-website/pull/89
This is an automated message from the Apache Git Service.
To respond to the
zregvart commented on a change in pull request #89: CAMEL-13889: website - Tab
title should be just Apache Camel
URL: https://github.com/apache/camel-website/pull/89#discussion_r324651160
##
File path: content/news/_index.md
##
@@ -1,5 +1,5 @@
---
-title: "Apache Camel
zregvart commented on a change in pull request #89: CAMEL-13889: website - Tab
title should be just Apache Camel
URL: https://github.com/apache/camel-website/pull/89#discussion_r324650750
##
File path: content/news/_index.md
##
@@ -1,5 +1,5 @@
---
-title: "Apache Camel
zregvart commented on issue #88: CAMEL-13818: design of the blog section
URL: https://github.com/apache/camel-website/pull/88#issuecomment-531758464
Here's [the
preview](https://builds.apache.org/job/Camel.website/job/PR-88/Preview/index.html).
alexkieling opened a new pull request #89: CAMEL-13889: website - Tab title
should be just Apache Camel
URL: https://github.com/apache/camel-website/pull/89
I've changed "Home page - Apache Camel" to "Home - Apache Camel".
I've also fixed the News page, which went from "Apache Camel
oscerd commented on issue #88: CAMEL-13818: design of the blog section
URL: https://github.com/apache/camel-website/pull/88#issuecomment-531722821
I already fixed the kubernetes part
This is an automated message from the
zregvart opened a new pull request #88: CAMEL-13818: design of the blog section
URL: https://github.com/apache/camel-website/pull/88
Summary of changes:
- news section renamed to blog
- blog section revamped with featured images
- headings are now bold (previously normal)
-
nicolaferraro commented on issue #933: Error after cluster restart
URL: https://github.com/apache/camel-k/issues/933#issuecomment-531686530
It's strange because objects being in state "Ready/Running" are almost not
touched by the state machine, so at cluster startup they should not be
zhfeng commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-531626067
@ffang [Quarks native
tips](https://quarkus.io/guides/writing-native-applications-tips#delay-class-initialization)
could be helpful with the failures.
WillemJiang edited a comment on issue #138: #137 Add the error log when setting
component property failed
URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-531560406
> The code you have linked relates to MissingPropertyException, not
PropertyBindingException
The
WillemJiang edited a comment on issue #138: #137 Add the error log when setting
component property failed
URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-531560406
> The code you have linked relates to MissingPropertyException, not
PropertyBindingException
The
WillemJiang commented on issue #138: #137 Add the error log when setting
component property failed
URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-531560406
> The code you have linked relates to MissingPropertyException, not
PropertyBindingException
Sorry,
lburgazzoli commented on issue #138: #137 Add the error log when setting
component property failed
URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-531550577
The code you have linked relates to MissingPropertyException, not
PropertyBindingException
WillemJiang commented on a change in pull request #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#discussion_r324442916
##
File path:
integration-tests/jira/src/main/java/org/apache/camel/quarkus/component/jira/it/JiraResource.java
##
@@ -0,0 +1,88
WillemJiang commented on a change in pull request #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#discussion_r324442848
##
File path: extensions/jira/deployment/pom.xml
##
@@ -0,0 +1,57 @@
+
Review comment:
Apache License header.
lubuxnl commented on issue #923: Camel-K build fails with error: open
/workspace/builder-656588331/package/context/Dockerfile: no such file or
directory
URL: https://github.com/apache/camel-k/issues/923#issuecomment-531505431
Still didn't find a solution, but I found a workaround for this
WillemJiang commented on issue #138: #137 Add the error log when setting
component property failed
URL: https://github.com/apache/camel-k-runtime/pull/138#issuecomment-531442837
> thinking a little bit more about this we may throw something like
>
> ```
> new
asf-ci commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-531424165
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/160/Build result:
FAILURE[...truncated
ffang commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-531413290
native build can make some progress, but I still see error like
`com.oracle.svm.core.util.UserError$UserException: No instances are allowed
in the image heap for a
asf-ci commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531413077
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/159/Failed
asf-ci commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531397519
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/158/Failed
asf-ci commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531371801
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/157/Build
ppalaga commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531369582
bdaeb18 adds the mojos to the component module.
I still have to figure out why the native test is timing out.
ppalaga commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531364334
39fcf89715a847d28f4e53e6f0f20734608710f2 : Addressed most of the points by
@lburgazzoli .
The native mode test is timing out saying
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324336543
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324336074
##
File path: extensions/platform-http/component/pom.xml
##
@@ -0,0 +1,57 @@
+
+
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324335692
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324335567
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324335301
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324335090
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324335215
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324334899
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324263195
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324288580
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324280445
##
File path: extensions/platform-http/component/pom.xml
##
@@ -0,0 +1,57 @@
+
+
bfitzpat closed issue #937: Monitoring kubectl for changes to integrations
misses transition to error state
URL: https://github.com/apache/camel-k/issues/937
This is an automated message from the Apache Git Service.
To
bfitzpat commented on issue #937: Monitoring kubectl for changes to
integrations misses transition to error state
URL: https://github.com/apache/camel-k/issues/937#issuecomment-531296435
Actually it was a watch timeout issue on my side, not the same issue as #906
- worked around the
lburgazzoli closed issue #906: Dev mode doesn't show if the build failed
URL: https://github.com/apache/camel-k/issues/906
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
lburgazzoli merged pull request #927: fix: Dev mode does not show if the build
failed
URL: https://github.com/apache/camel-k/pull/927
This is an automated message from the Apache Git Service.
To respond to the message,
bfitzpat commented on issue #937: Monitoring kubectl for changes to
integrations misses transition to error state
URL: https://github.com/apache/camel-k/issues/937#issuecomment-531283549
Looks like the same issue is being seen here -
https://github.com/apache/camel-k/issues/906
bfitzpat commented on issue #937: Monitoring kubectl for changes to
integrations misses transition to error state
URL: https://github.com/apache/camel-k/issues/937#issuecomment-531280065
Looks like "kubectl get" has a timeout as well. If nothing in the system
changes after a few seconds,
bfitzpat opened a new issue #937: Monitoring kubectl for changes to
integrations misses transition to error state
URL: https://github.com/apache/camel-k/issues/937
So I've started looking at auto-refresh in the tooling and hit upon a fun
little issue.
If I use "kubectl get
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324218757
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r32413
##
File path:
oscerd merged pull request #936: fix(examples): Remove timer route to allow
scale-to-zero of REST DSL example
URL: https://github.com/apache/camel-k/pull/936
This is an automated message from the Apache Git Service.
To
zregvart merged pull request #87: fix: update wrong mailing list information
URL: https://github.com/apache/camel-website/pull/87
This is an automated message from the Apache Git Service.
To respond to the message, please
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324184251
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324181915
##
File path:
ppalaga commented on a change in pull request #201: Fix #184 Leverage platform
http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324181581
##
File path:
astefanutti opened a new pull request #936: fix(examples): Remove timer route
to allow scale-to-zero of REST DSL example
URL: https://github.com/apache/camel-k/pull/936
This is an automated message from the Apache Git
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324161202
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324164804
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324163568
##
File path: extensions/platform-http/component/pom.xml
##
@@ -0,0 +1,57 @@
+
+
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324162374
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324161524
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324167970
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324163268
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324161759
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324162643
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324166313
##
File path:
lburgazzoli commented on a change in pull request #201: Fix #184 Leverage
platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#discussion_r324160639
##
File path:
zregvart opened a new pull request #87: fix: update wrong mailing list
information
URL: https://github.com/apache/camel-website/pull/87
This is an automated message from the Apache Git Service.
To respond to the message,
asf-ci commented on issue #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201#issuecomment-531213725
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/156/Build
ppalaga opened a new pull request #201: Fix #184 Leverage platform http service
URL: https://github.com/apache/camel-quarkus/pull/201
This is an automated message from the Apache Git Service.
To respond to the message,
ppalaga commented on issue #184: Leverage platform http service
URL: https://github.com/apache/camel-quarkus/issues/184#issuecomment-531165704
> How should the URI scheme be called? `http-server` maybe?
Going with `platform-http` after a discussion with @lburgazzoli
astefanutti commented on a change in pull request #922: fix: Add option to
disable Kaniko cache warming
URL: https://github.com/apache/camel-k/pull/922#discussion_r323816673
##
File path: pkg/controller/integrationplatform/initialize.go
##
@@ -137,7 +137,7 @@ func (action
astefanutti opened a new pull request #935: fix(knative): Use channel hostname
to filter Knative history header
URL: https://github.com/apache/camel-k/pull/935
This is an automated message from the Apache Git Service.
To
lburgazzoli opened a new issue #934: User profiles
URL: https://github.com/apache/camel-k/issues/934
As today we have a profile concept but it is related only to the platform ,
we should introduce a user profile concept as a way to share common options
among integrations
ffang commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-530848125
I'm investigating the build failure
This is an automated message from the Apache Git Service.
To respond
asf-ci commented on issue #189: Make xml and jaxb disabled by default and
opt-in when depending on camel
URL: https://github.com/apache/camel-quarkus/pull/189#issuecomment-530836969
Refer to this link for build results (access rights to CI server needed):
lburgazzoli commented on issue #198: Remove support for RuntimeValue from
registry
URL: https://github.com/apache/camel-quarkus/issues/198#issuecomment-530742898
Digging into it a little bit more, we can use
ppalaga commented on issue #200: improve the paho integration test
URL: https://github.com/apache/camel-quarkus/pull/200#issuecomment-530696348
@zhfeng perfect, thanks!
This is an automated message from the Apache Git
oscerd merged pull request #200: improve the paho integration test
URL: https://github.com/apache/camel-quarkus/pull/200
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
asf-ci commented on issue #200: improve the paho integration test
URL: https://github.com/apache/camel-quarkus/pull/200#issuecomment-530642232
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/154/
zhfeng commented on issue #200: improve the paho integration test
URL: https://github.com/apache/camel-quarkus/pull/200#issuecomment-530629972
@ppalaga I make some changes to improve the paho test to check the message
after publishing to the queue. Can you take a look ?
zhfeng opened a new pull request #200: improve the paho integration test
URL: https://github.com/apache/camel-quarkus/pull/200
This is an automated message from the Apache Git Service.
To respond to the message, please log
asf-ci commented on issue #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199#issuecomment-530603827
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/153/Build result:
FAILURE[...truncated
ffang opened a new pull request #199: Camel jira
URL: https://github.com/apache/camel-quarkus/pull/199
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
lburgazzoli opened a new issue #198: Remove support for RuntimeValue from
registry
URL: https://github.com/apache/camel-quarkus/issues/198
It does not seem we do store instances wrapped by a RuntimeValue in the
registry any more so it may be possible to thing to simplify the registry and
weimeilin79 opened a new issue #933: Error after cluster restart
URL: https://github.com/apache/camel-k/issues/933
Error appears when cluster restarts.
CRD missing.
oscerd merged pull request #139: yaml-loader: support route definition
URL: https://github.com/apache/camel-k-runtime/pull/139
This is an automated message from the Apache Git Service.
To respond to the message, please log
oscerd merged pull request #140: fix(catalog): Declare the webhook component as
an HTTP component
URL: https://github.com/apache/camel-k-runtime/pull/140
This is an automated message from the Apache Git Service.
To respond
901 - 1000 of 5598 matches
Mail list logo
