[GitHub] [pulsar-client-node] savearray2 opened a new issue #119: Unhandled Promise Rejection On Failed createProducer

savearray2 opened a new issue #119: URL: https://github.com/apache/pulsar-client-node/issues/119 When creating a producer using a client URL that is intentionally incorrect via the following: ```js const client = new Pulsar.Client({ serviceUrl: 'pulsar://this-will-fail:6650',

Re: [VOTE] Pulsar Manager Release 0.2.0 Candidate 3

+1 - checked checksums and signatures (I suggest you to add your signature to https://dist.apache.org/repos/dist/release/pulsar/KEYS as well, as the other one is on "dev") - run tests on Java8, Mac and Fedora Linux(it is unfortunate that we can't build it on JDK11, I will send a PR soon) - tested

[VOTE] Pulsar Manager Release 0.2.0 Candidate 3

Hi everyone, Please review and vote on the release candidate #3 for the version 0.2.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * Release notes [1] https://g

[GitHub] [pulsar-dotpulsar] usaguerrilla commented on issue #56: If server dies Consumer / Producer Channel sometimes goes into faulted state and never tries to reconnect

usaguerrilla commented on issue #56: URL: https://github.com/apache/pulsar-dotpulsar/issues/56#issuecomment-690640525 In some sense if we bail on reconnecting and mark consumer / producer as invalid in some cases, why not bail all the time? IMHO consistency is way better than having stuff

[GitHub] [pulsar-dotpulsar] usaguerrilla commented on issue #56: If server dies Consumer / Producer Channel sometimes goes into faulted state and never tries to reconnect

usaguerrilla commented on issue #56: URL: https://github.com/apache/pulsar-dotpulsar/issues/56#issuecomment-690628136 So consumer is trying to reconnect during server shutting down (or crash) and it gets this: ```Unable to read data from the transport connection: An established conn

[GitHub] [pulsar-dotpulsar] usaguerrilla edited a comment on issue #56: If server dies Consumer / Producer Channel sometimes goes into faulted state and never tries to reconnect

usaguerrilla edited a comment on issue #56: URL: https://github.com/apache/pulsar-dotpulsar/issues/56#issuecomment-690586257 I will think more but one problem here is that not all commands are initiated (and sent, e.g. flow / subscribe commands) by the client. It also affects consumer. If

[GitHub] [pulsar-dotpulsar] usaguerrilla commented on issue #56: If server dies Consumer / Producer Channel sometimes goes into faulted state and never tries to reconnect

usaguerrilla commented on issue #56: URL: https://github.com/apache/pulsar-dotpulsar/issues/56#issuecomment-690586257 I will think more but one problem here is that not all commands are initiated by the client. It also affects consumer. If server shuts down when consumer was sending flow c

Re: [VOTE] Pulsar Manager Release 0.2.0 Candidate 2

Sorry, I know the reason. I will start a new vote again. Thanks, Guangning Enrico Olivelli 于2020年9月10日周四 下午7:07写道： > Guangning, > great to see the new version of BKVM, thank you. > > It looks like my comment on RC0 was not addressed: the source tarball > apache-pulsar-manager-0.2.0-src.tar.gz

Re: [VOTE] Pulsar Manager Release 0.2.0 Candidate 2

Guangning, great to see the new version of BKVM, thank you. It looks like my comment on RC0 was not addressed: the source tarball apache-pulsar-manager-0.2.0-src.tar.gz

Slack digest for #dev - 2020-09-10

2020-09-09 11:26:41 UTC - Gabriel Volpe: @Gabriel Volpe has joined the channel 2020-09-09 11:28:30 UTC - Gabriel Volpe: Is this the appropriate channel to ask questions about the protocol? I'll go ahead and ask here but feel free to point me to the right channel if this is not the one.