Hi Dave,
Will follow up tomorrow morning (Pacific Time).
- Sijie
On Wed, Dec 8, 2021 at 9:35 PM Dave Fisher wrote:
> Hi Sijie,
>
> Thanks for handling this issue. I’ll check in my morning. There was a
> reference on the Community Newsletter as well. Please check that too.
>
> Best Regards,
>
massakam opened a new pull request #186:
URL: https://github.com/apache/pulsar-client-node/pull/186
Updated the dependent packages to the latest version with the same major
version. `node-pre-gyp` has already been deprecated, so replaced it with an
alternative package
Hi Sijie,
Thanks for handling this issue. I’ll check in my morning. There was a reference
on the Community Newsletter as well. Please check that too.
Best Regards,
Dave
Sent from my iPhone
> On Dec 8, 2021, at 9:24 PM, Sijie Guo wrote:
>
> Dave,
>
> I think that is a mistake. We already
+1 on this proposal.
For the details, I think we should consider avoiding the breaking change
for the existing broker interceptor(make sure the old interceptor can still
work),
Penghui
On Wed, Dec 8, 2021 at 12:56 PM Sijie Guo wrote:
> Agree with Matteo.
>
> +1 on this proposal.
>
> On Tue,
Dave,
I think that is a mistake. We already caught it. Dianjin is fixing it.
- Sijie
On Wed, Dec 8, 2021 at 11:41 AM Dave Fisher wrote:
> This is great news!
>
> However the ending of the blog post [1] does not follow the Apache Way
>
> This bullet point is misleading and serves to split the
shiv4289 commented on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-989513467
@tuteng @eolivelli Can you please approve the test workflow run?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
shiv4289 commented on pull request #434:
URL: https://github.com/apache/pulsar-manager/pull/434#issuecomment-989512721
This is an important change for us. Pulsar manager not integrating with our
SSO is a huge roadblock for pulsar manager adoption. Great work
@sourabhaggrawal . Lets sprint
+1
On Wed, Dec 8, 2021 at 8:37 PM Masahiro Sakamoto
wrote:
> Hi Team,
>
> I'm planning to release v1.5.0 of the Pulsar Node.js client next week as
> some bug fixes have been merged to master.
> If you have any comments on this, please reply to this email.
>
> Regards,
>
> Masahiro Sakamoto
>
massakam opened a new pull request #185:
URL: https://github.com/apache/pulsar-client-node/pull/185
Added v1.5.x of the Node.js client to the table in `README.md`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Hi Team,
I'm planning to release v1.5.0 of the Pulsar Node.js client next week as some
bug fixes have been merged to master.
If you have any comments on this, please reply to this email.
Regards,
Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp
sourabhaggrawal commented on pull request #434:
URL: https://github.com/apache/pulsar-manager/pull/434#issuecomment-989494897
Hello @tuteng @eolivelli Please take a look, I will add test cases for same
if changes good to you.
--
This is an automated message from the Apache Git Service.
sourabhaggrawal opened a new pull request #434:
URL: https://github.com/apache/pulsar-manager/pull/434
### Motivation
Idea is to support authentication from ThirdParty using SAML Approach.
Changes are backward compatible and existing Login Approach using credentials
will continue to
This is great news!
However the ending of the blog post [1] does not follow the Apache Way
This bullet point is misleading and serves to split the community.
> • Join the 2022 Pulsar Ambassador Program and work directly with Pulsar PMCs
> and top contributors to co-host events, promote new
sourabhaggrawal commented on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-988959960
Hi @tuteng Thanks for the suggestion and looks like the build is triggered.
I see 1 workflow is waiting for an approval. Can you please help me get it
resolved
tuteng commented on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-988890739
I don't seem to be able to re-run the build either, I think you could do an
empty commit and push to this branch again and that might re-trigger the build.
@sourabhaggrawal
sourabhaggrawal edited a comment on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-92149
Hi @tuteng the change is in sql file to create an index and should not
impact any existing test case.
Below is the test case which is failing
sourabhaggrawal commented on pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420#issuecomment-92149
Hi @tuteng the change is in sql file to create an index and should not
impact any existing test case.
Below is the test case which is failing
blankensteiner commented on issue #8:
URL: https://github.com/apache/pulsar-dotpulsar/issues/8#issuecomment-988805576
Hi @johnboy007 it's not a feature we (Danske Commodities) are using, but we
will be happy to discuss the implementation and review and merge a PR solving
this :-)
--
blankensteiner commented on issue #6:
URL: https://github.com/apache/pulsar-dotpulsar/issues/6#issuecomment-988804472
Hi @johnboy007 it's not something that is being worked on currently. A PR is
most welcome :-)
--
This is an automated message from the Apache Git Service.
To respond to
johnboy007 commented on issue #6:
URL: https://github.com/apache/pulsar-dotpulsar/issues/6#issuecomment-988793327
Hi do you know when Protobuf, JSON, and Avro will be supported?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
Hi Pulsar Community,
Currently, only super-user and tenant-administrator can set/get/remove the
subscription policies of the namespace. The subscription policies includes:
subscription-expiration-time
subscription-auth-mode
subscription-types-enabled
subscription-dispatch-rate
massakam opened a new pull request #184:
URL: https://github.com/apache/pulsar-client-node/pull/184
Recently, the release process for the Node.js client has been modified and
added a step to create a tarball of this repository.
```sh
# Archive the source files
$ git archive HEAD
22 matches
Mail list logo
