Hello all:
I will cut the 0.4.0 of go client, thanks everyone for this.
--
Thanks
Xiaolong Ran
在 2021年1月30日 +0800 PM3:10，xiaolong ran ，写道：
> Hello all:
>
> I hope you've all been doing well. Since the last v0.3.0 release,
> almost two months and a half have passed. So I will start to release
> v
Hi everyone,
Please review and vote on the release candidate #1 for the version 0.4.0, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This is the first release candidate for Apache Pulsar Go client, version 0.4.0.
It fixes the follow
Hello all:
I will cut the 0.4.0 of go client, thanks everyone for this.
--
Thanks
Xiaolong Ran
在 2021年1月30日 +0800 PM3:10，xiaolong ran ，写道：
> Hello all:
>
> I hope you've all been doing well. Since the last v0.3.0 release,
> almost two months and a half have passed. So I will start to release
> v
Hi everyone,
Please review and vote on the release candidate #1 for the version 0.4.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This is the first release candidate for Apache Pulsar Go client, version
0.4.0.
It fixes the fo
massakam commented on issue #22:
URL:
https://github.com/apache/pulsar-client-node/issues/22#issuecomment-775624048
@bwalendz @rkaw92
I have added the type definitions to this repository:
https://github.com/apache/pulsar-client-node/pull/140
---
Michael,
Thank you for your comment!
> Which Pulsar Clients will benefit from this proposal?
I think that this proposal will be useful to any clients.
In my schedule, if this proposal is accepted then I will implement this feature
to Java client.
If needed, then implement same feature to other c
massakam opened a new pull request #140:
URL: https://github.com/apache/pulsar-client-node/pull/140
Added the type definition file for `pulsar-client`. This makes
`pulsar-client` available in TypeScript.
This is an automated
jiazhai closed issue #12:
URL: https://github.com/apache/pulsar-test-infra/issues/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
jiazhai merged pull request #16:
URL: https://github.com/apache/pulsar-test-infra/pull/16
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
hrsakai commented on issue #134:
URL:
https://github.com/apache/pulsar-client-node/issues/134#issuecomment-775578576
> Does this section of the error log ring any bells?:
No, please ignore that log.
We haven't uploaded libpulsar.node to the remote server.
---
Hi Jonathan,
Thanks for giving thought to this subject. I think we can all agree that
increasing public awareness of the momentum and community strength behind
Pulsar is a common goal among members of the Pulsar community. I'm sure
many of us have run into similar challenges with increasing adopti
tschmidt64-SC commented on issue #134:
URL:
https://github.com/apache/pulsar-client-node/issues/134#issuecomment-775365944
Does this section of the error log ring any bells?:
```
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp info check checked for
"
tschmidt64-SC commented on issue #134:
URL:
https://github.com/apache/pulsar-client-node/issues/134#issuecomment-775359167
I'm on 1.2.1 currently. I'll look into node-gyp and see if I can get it
resolved that direction. Will report back after.
I checked the ASF mail archives to make sure this went through and realized
that somehow gmail stripped all paragraphing from my reply. Trying again:
I thank Sijie for the comment on my pull request [1]. I’m following up
here because I think this is the kind of discussion best suited for the
mai
lhotari commented on pull request #16:
URL: https://github.com/apache/pulsar-test-infra/pull/16#issuecomment-775219893
Another improvement in using `diff-only` would be to switch from using
```
if: steps.docs.outputs.changed_only == 'no'
```
to
```
if: steps.docs.outputs.ch
Thanks for the proposal Enrico.
On Mon, Feb 8, 2021 at 12:32 PM Enrico Olivelli wrote:
> 2) Building Pulsar and running Tests
> We can require Pulsar to be built on JDK11.
> We can set maven.compiler.release to 11 in generale and
> maven.compiler.release to 8 for all of the modules that concur
Thanks for reporting the issue Enrico.
The root cause of this is fixed in
https://github.com/apache/pulsar-test-infra/pull/16 .
*It happens for pull requests with more than 25 commits since we are using
shallow clones because of performance reasons. *
*The shallow clone change was made in
https://
miecio45 opened a new pull request #104:
URL: https://github.com/apache/pulsar-helm-chart/pull/104
Adds dynamic superusers configuration
### Motivation
Allow dynamic superusers management. Adding new superuser entry to
`.Values.auth.superUsers` will results in adding concatena
lhotari opened a new pull request #16:
URL: https://github.com/apache/pulsar-test-infra/pull/16
Fixes #12 https://github.com/apache/pulsar/issues/9526
The current solution causes the build to skip tests in Pulsar builds when
the pull request commits cannot be found. It's better that
Hello,
today I saw that the GH queue was pretty empty.
And I also realized that my PRs had been validated super quickly.
I saw this problem, basically CI is no more validating PRs.
The bad thing is that CI is reported as GREEN !
I created this issue in order to track the problem
https://github.c
Hello Pulsar community,
I would like to start a discussion about Java 11 support and about dropping
support for JDK8 on the server side.
It will take time, see my points below.
At the moment we have these use cases about Java compatibility:
- Java client users
- Building Pulsar and running Pulsar
21 matches
Mail list logo
