This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

FYI https://apache-pulsar.slack.com/archives/C01DGCB0KPU/p1673596492049309

This message was deleted.

@Yu Wei Sung has left the channel

While the new site looks good and all. I have a serious question about how the sitemap.xml file is generated. In addition we must do something so that search engines will index and find documentation for Pulsar 3.0.0 before 2.4.2!!!!

I don’t think the new site has changed in good or bad any of these 2 aspects 🙂

sitemap.xml should be getting generated by docusarus

Sure. I just had the joy of recloning because of the reorg. I'm just really curious how we can get the search engines to do better. I aslo recently had a fight with an LLM that was confused by bad training.

grep does not help me find a thread about how the sitemap is generated - although I know that it is as (a single line xml)

% grep -rni sitemap
./yarn.lock:2172:"@docusaurus/plugin-sitemap@npm:2.4.0":
./yarn.lock:2174:  resolution: "@docusaurus/plugin-sitemap@npm:2.4.0"
./yarn.lock:2183:    sitemap: ^7.1.1
./yarn.lock:2204:    "@docusaurus/plugin-sitemap": 2.4.0
./yarn.lock:12829:"sitemap@npm:^7.1.1":
./yarn.lock:12831:  resolution: "sitemap@npm:7.1.1"
./yarn.lock:12838:    sitemap: dist/cli.js
./static/robots.txt:1:Sitemap: <https://pulsar.apache.org/sitemap.xml>

https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-sitemap It looks like we take the defaults ....

Also - we are now using Matomo and ASF Privacy wants everyone to drop Google Analytics, but GA is still on our pages.

<link rel="preconnect" href="<https://www.google-analytics.com>">
<script><http://window.ga|window.ga>=<http://window.ga|window.ga>||function(){(ga.q=ga.q||[]).push(arguments)},ga.l=+new Date,ga("create","UA-102219959-1","auto"),ga("send","pageview")</script>

This is against the GPDR.

This message was deleted.

@eric jiang has left the channel

I'm currently trying to set

managedLedgerMaxEntriesPerLedger

for the PulsarContainer in a test. However, this setting (max 1 entry per ledger) is not being reflected in my tests, as when I try to write multiple entries to a topic or topic-partition, I see multiple entries in each ledger. Here is the relevant commit. Can anyone help me here or point me in a direction I can get help from?

This message was deleted.

Hello. Please can someone help review this PR: https://github.com/apache/pulsar/pull/21077

I'm fixing flaky test issues and would appreciate a review on this PR so that it could be merged: https://github.com/apache/pulsar/pull/21407

There's now a solution for reporting and detecting thread leaks in tests. It should be ensured in each test that resources created by the test are properly cleaned up. Failing to do so can lead to memory leaks and, in some instances, unnecessary CPU consumption. These issues can, in turn, slow down test execution, increase Pulsar CI build durations, and cause flakiness. A significant source of memory leaks in Pulsar tests stems from thread leaks. dev mailing list thread: https://lists.apache.org/thread/l0h9qd5vwzdx30sqw5vocwkdjxh1gqzt PR: https://github.com/apache/pulsar/pull/21450 Please review the PR so that we get this solution in place. Thanks!

Hi! Could someone check this PR? Please tell me if there's more appropriate way to request review. Thanks, https://github.com/apache/pulsar-site/pull/923

@ocadaruma Hi, I merged your PR.

Thank you!

Can I get review on this PR: https://github.com/streamnative/pulsar-spark/pull/180 that bumps the Pulsar version up from 2.10 to 3.3 for the pulsar-spark connector? We found a race condition in Pulsar 2.10