I have requested INFRA to revert the change -
https://issues.apache.org/jira/browse/INFRA-19545 and also pinged them in
the ASF Slack channel.
Please make sure any conversations happen on the mailing list first before
requesting INFRA changes in the future.
Thanks,
Sijie
On Mon, Dec 16, 2019 at
They are few issues I see I am compiling PR's for them. We list them here
I will find time to fix them.
On Mon, Dec 16, 2019 at 10:44 PM Sijie Guo wrote:
> Hi Ali,
>
> Thank you for compiling the issues together.
>
> However, I think the immediate action is to ask INFRA to revert the
> settin
Hi Ali,
Thank you for compiling the issues together.
However, I think the immediate action is to ask INFRA to revert the
settings back to make Jenkins CI as required.
Here is the reason:
1) I don't think the Github Actions are stable enough to cover Jenkins CI.
There are still Github Actions tha
If some one is noticing specific issues please let me know I will fix them.
-Ali
On Mon, Dec 16, 2019 at 10:37 PM Ali Ahmed wrote:
> Github actions went live there have been some reported . am looking into
> them. Here are the issues compiled below.
>
> 1) Some PR's are stuck and don't run gith
Github actions went live there have been some reported . am looking into
them. Here are the issues compiled below.
1) Some PR's are stuck and don't run github actions.
They are two reasons for these one they are not rebased with giithub
workflow changes.
They are markdown only changes in the pr t
Thanks @xiaolong for rising up this discussion.
Apache BookKeeper uses a script to do the PR merge, and the script could
handle cherry-pick into old branch if needed. This could avoid cherry-pick
at the release time.
Best Regards.
Jia Zhai
Beijing, China
Mobile: +86 15810491983
On Tue, De
mhaagens commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566141084
Awesome, thanks!
This is an automated message from the Apache Git Service.
To respond
david-streamlio commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566139450
@mhaagens Not yet, but there appears to be a PR in process now to add this
capability. https://github.com/apache/pulsar-client-node/pull/56
mhaagens commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566137312
Okay, so am I understanding it correctly that there’s no way to set up a
listener that processes messages as they come in? Similar to this in kafka-Nod
david-streamlio commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566134248
@mhaagens You are correct. The `subscribe` command is used to register your
consumer on the Pulsar broker, so it will know that you want to rece
mhaagens commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566132032
Thanks for the quick reply! I am using subscribe, but as far I can see from
the example you have to manually call receive on the subscriber in a loop t
david-streamlio commented on issue #62: Listening for messages
URL:
https://github.com/apache/pulsar-client-node/issues/62#issuecomment-566126386
@mhaagens In order to receive messages, you will want to use the `subscribe`
method as shown in the following example:
https://github.com/apac
mhaagens opened a new issue #62: Listening for messages
URL: https://github.com/apache/pulsar-client-node/issues/62
How can I listen to incoming messages? The `listener` property on consumer
doesn't seem to do anything.
This
2019-12-15 21:06:28 UTC - Jared Mackey: @Jared Mackey has joined the channel
2019-12-16 03:43:30 UTC - Ali Ahmed: apache jenkins jobs have been removed from
the required list for pr’s in favor or select github actions.
2019-12-16 03:46:21 UTC - xiaolong.ran: Thanks @Ali Ahmed but it does
14 matches
Mail list logo
