Hi folks,
I noticed that we write a lot of logic to handle ancient documents back to
the incubating period on the current doc site syncing and building. It
causes unnecessary maintenance burdens as well as more broken links due to
different document frameworks.
Since those ancient documents have
arnarg commented on PR #291:
URL:
https://github.com/apache/pulsar-helm-chart/pull/291#issuecomment-1280422676
Doesn't seem like the failing workflows are because of my changes, right?
@michaeljmarshall
--
This is an automated message from the Apache Git Service.
To respond to the messa
+1(non-binding)
- Checked signatures/checksums
- Built from sources using `mvn clean install -DskipTests` using JDK 17
- Run the standalone
- Validate Connectors
- Validate Pub/Sub and Java Functions
- Validate Stateful Functions
Michael Marshall 于2022年10月17日周一 12:31写道：
> +1 (binding)
>
> - Veri
Hi tison,
Thanks for taking care of the docs!
Seems that archiving the incubating docs does not affect the existing
workflow of Pulsar doc update/maintenance.
+1 for this proposal.
Yu
On Mon, Oct 17, 2022 at 3:24 PM tison wrote:
> Hi folks,
>
> I noticed that we write a lot of logic to handle
Hi
Sorry for the late release, we need to wait for the 2 fixes on the BK
side.
https://github.com/apache/bookkeeper/pull/3523
https://github.com/apache/bookkeeper/pull/3528
Regards
Jiwei Guo (Tboy)
On Fri, Oct 14, 2022 at 6:02 AM Christophe Bornet
wrote:
> The blockers mentioned by Nico
Dear community,
Here's a report of the flaky tests in Pulsar CI during the observation
period of 2022-10-07 - 2022-10-14
https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit?usp=sharing
The report contains a subset of the test failures.
The flaky tests are o
amareshmad commented on issue #114:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1280725410
Connection established from product code
Consumer code:
await using var client = PulsarClient.Builder()
blankensteiner closed issue #114: When i run test console app consumer is
creating and when i integrate same to actual product consumer is not creating
and going to Faulted state
URL: https://github.com/apache/pulsar-dotpulsar/issues/114
--
This is an automated message from the Apache Git Se
blankensteiner commented on issue #114:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1280794621
Glad to hear it. TLS can be tricky :-)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
michaeljmarshall commented on PR #291:
URL:
https://github.com/apache/pulsar-helm-chart/pull/291#issuecomment-1280978613
No, these might just be flaky workflows. I triggered the failed jobs to run
again.
--
This is an automated message from the Apache Git Service.
To respond to the messa
michaeljmarshall opened a new pull request, #115:
URL: https://github.com/apache/pulsar-dotpulsar/pull/115
This PR modifies the Apache mailing list notifications so that commits,
issues, and pull request notifications are sent to the
comm...@pulsar.apache.org mailing list. If you would like
michaeljmarshall opened a new pull request, #302:
URL: https://github.com/apache/pulsar-helm-chart/pull/302
This PR modifies the Apache mailing list notifications so that commits,
issues, and pull request notifications are sent to the
comm...@pulsar.apache.org mailing list. If you would lik
michaeljmarshall opened a new pull request, #236:
URL: https://github.com/apache/pulsar-client-node/pull/236
This PR modifies the Apache mailing list notifications so that commits,
issues, and pull request notifications are sent to the
comm...@pulsar.apache.org mailing list. If you would li
michaeljmarshall merged PR #236:
URL: https://github.com/apache/pulsar-client-node/pull/236
--
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 the specific comment.
To unsubscribe, e-mail: dev-unsubscr
michaeljmarshall merged PR #302:
URL: https://github.com/apache/pulsar-helm-chart/pull/302
--
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 the specific comment.
To unsubscribe, e-mail: dev-unsubscr.
michaeljmarshall merged PR #115:
URL: https://github.com/apache/pulsar-dotpulsar/pull/115
--
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 the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
I merged the following PRs as a result of this discussion:
https://github.com/apache/pulsar-client-node/pull/236
https://github.com/apache/pulsar-client-go/pull/861
https://github.com/apache/pulsar-helm-chart/pull/302
https://github.com/apache/pulsar-dotpulsar/pull/115
If you would like to get gr
Hi Enrico,
We internally did PoC work and presented the demo(local bundle state
channel test) in the Apache Con 2022 NA.
We just started raising PRs for this project, and we will be tagging the PR
titles with [pip-192].
Thank you,
Heesung
On Wed, Oct 12, 2022 at 11:33 PM Enrico Olivelli
wrot
Thank you all.
Closing this vote with 3 binding +1s and 2 non-binding +1s.
Thanks,
Haiting
On Mon, Oct 17, 2022 at 3:57 PM Qiang Huang wrote:
>
> +1(non-binding)
> - Checked signatures/checksums
> - Built from sources using `mvn clean install -DskipTests` using JDK 17
> - Run the standalone
> -
19 matches
Mail list logo
