Build failed in Jenkins: pulsar_release_nightly_snapshot #757

See Changes: [github] [PulsarAdmin] Brokers to async (#6541) [github] Add more logging during refresh credentials path (#6551) [github] [functions] Default functionAuthProvider when running in k8s

[GitHub] [pulsar-client-node] yosiat edited a comment on issue #78: Error: Failed to send message: AlreadyClosed

yosiat edited a comment on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-601193248 @alexyans yeah this is an example, but in real system, I want to use the same producer and publish messages every now and

[GitHub] [pulsar-client-node] yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed

yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-601193248 @alexyans yeah this is an example, but in real system, I want to use the same producer and publish messages every now and then. we

[GitHub] [pulsar-client-node] alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed

alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-601179535 This is a playground example though. In a real system you can't necessarily control the rate of messages produced, as they corre

#TGIPulsar Episode 002 - Kubernetes Deployment

Hi all, Our weekly live stream "TGI Pulsar" ( https://www.youtube.com/channel/UCywxUI5HlIyc0VEKYR4X9Pg/live) continues this week. Pulsar was architected to run easily on cloud-native environments. It is very easy to spin up a cluster on Kubernetes. But there are also some considerations and best p

[GitHub] [pulsar-client-node] yosiat commented on issue #62: Listening for messages

yosiat commented on issue #62: Listening for messages URL: https://github.com/apache/pulsar-client-node/issues/62#issuecomment-601155467 @sijie created a PR, here: https://github.com/apache/pulsar-client-node/pull/83 This is

[GitHub] [pulsar-client-node] yosiat commented on a change in pull request #83: Consumer with message listener dies after some time

yosiat commented on a change in pull request #83: Consumer with message listener dies after some time URL: https://github.com/apache/pulsar-client-node/pull/83#discussion_r394994930 ## File path: src/Consumer.cc ## @@ -45,6 +45,37 @@ void Consumer::Init(Napi::Env env, Napi

[GitHub] [pulsar-client-node] yosiat opened a new pull request #83: Consumer with message listener dies after some time

yosiat opened a new pull request #83: Consumer with message listener dies after some time URL: https://github.com/apache/pulsar-client-node/pull/83 This PR: - Moves message listener to consumer - Use a single consumer instance The issue I am solving can be reproduced here: `

[GitHub] [pulsar-client-node] yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed

yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-601153727 How I avoid client destruction? In the following example, I create a producer and produce a message every 1 second.

Slack digest for #dev - 2020-03-19

2020-03-19 06:11:41 UTC - Pushkar Sawant: @Pushkar Sawant has joined the channel