[GitHub] [pulsar-manager] urfreespace opened a new pull request #455: Move version to 0.3.0
urfreespace opened a new pull request #455: URL: https://github.com/apache/pulsar-manager/pull/455 * Move version to 0.3.0 -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-client-node] Matt-Esch commented on pull request #200: convert worker threads to async functions
Matt-Esch commented on pull request #200: URL: https://github.com/apache/pulsar-client-node/pull/200#issuecomment-1082828552 Tests are passing: https://github.com/Matt-Esch/pulsar-client-node/actions/runs/2033472853 Comments have been addressed. Are we ready to accept this pr and merge? -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[VOTE] Pulsar Manager Release 0.3.0 Candidate 1
Hi everyone, Please review and vote on the release candidate #1 for the version 0.3.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] * The official Apache source and binary distributions to be deployed to dist.apache.org [2] * Source code tag "v0.3.0-candidate-1" [4] with git sha 2396bf10127ec3b23c110edd87df36a422d180f972f60f88e04f96bd8b583b3eac1f0bb3cfccb9541fb2667fca56159bdb7cf71d0a314c948439862d087145f0 apache-pulsar-manager-0.3.0-src.tar.gz PulsarManager's KEYS file contains PGP keys we used to sign this release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download these packages and review this release candidate: - Review release notes - Download the source package (verify shasum, and asc) and follow the instructions to build and run the pulsar-manager front end and back end service. - Download the binary package (verify shasum, and asc) and follow the instructions to run run the pulsar-manager front end and back end service. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source and binary files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz SHA-512 checksums: 9fd3148c31515f3f2d2d3620abfd669a6ced729e586b921cdc74c197e99909c5e9def2f03652c33fbbdffabdf5b60c428676cc14a3a4b0556a1487f2d6fe18a0 apache-pulsar-manager-0.3.0-bin.tar.gz 2396bf10127ec3b23c110edd87df36a422d180f972f60f88e04f96bd8b583b3eac1f0bb3cfccb9541fb2667fca56159bdb7cf71d0a314c948439862d087145f0 apache-pulsar-manager-0.3.0-src.tar.gz
[GitHub] [pulsar-manager] zy857189690 commented on issue #454: Bookies table displays nothing and NPE happens in pulsar-manager.log
zy857189690 commented on issue #454: URL: https://github.com/apache/pulsar-manager/issues/454#issuecomment-1082923116 me too -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"
Merging the PR is blocked by https://github.com/apache/pulsar/issues/14951 . Pulsar SQL doesn't work with Java 11.0.14.1 version. It fails with this error message: Exception in thread "main" java.lang.IllegalArgumentException: Cannot parse version 11.0.14.1 at io.prestosql.server.JavaVersion.parse(JavaVersion.java:76) at io.prestosql.server.PrestoSystemRequirements.verifyJavaVersion(PrestoSystemRequirements.java:102) at io.prestosql.server.PrestoSystemRequirements.verifyJvmRequirements(PrestoSystemRequirements.java:45) at io.prestosql.server.PrestoServer.run(PrestoServer.java:78) at io.prestosql.$gen.Presto_33220220330_100314_1.run(Unknown Source) at io.prestosql.server.PrestoServer.main(PrestoServer.java:72) I'll apply a workaround to unblock CI. -Lari On 2022/03/30 06:52:38 Lari Hotari wrote: > Thank you for the reviews and feedback. I have started making the switch to > the new refactored Pulsar CI. > > Merging new PRs are blocked until the switch is ready. The reason for this is > that I have merged https://github.com/apache/pulsar/pull/14939 preparing for > merging https://github.com/apache/pulsar/pull/14819 . > > The GitHub Actions "required checks" change in the refactored Pulsar CI and > there can be only one effective set of "required checks" for a branch. > > After the new Pulsar CI workflow PR has been merged, each in-progress PR has > to be closed & immediately reopened to pick up the new workflow and the PR > build has to run through the new workflow. Another way to pick up the new > workflow is to rebase the PR (or merge master branch changes to it). > > Please let me know if you experience any issues with the new Pulsar CI > workflow. I'll be on the #testing channel on Pulsar Slack too. > > -Lari > > On 2022/03/29 15:43:31 Michael Marshall wrote: > > Great work, Lari! It's great news that GitHub's new feature helps this > > valuable work move forward. I look forward to seeing your PR merged, > > and I am happy to help resolve any issues that might pop up. > > > > Thanks, > > Michael > > > > On Tue, Mar 29, 2022 at 7:55 AM Lari Hotari wrote: > > > > > > The PR has sufficient reviews, and I'll proceed with merging it today or > > > tomorrow. > > > Please provide feedback now if you want to do that before the PR is > > > merged. > > > > > > Thanks! > > > > > > -Lari > > > > > > On 2022/03/28 20:05:14 Lari Hotari wrote: > > > > The PR https://github.com/apache/pulsar/pull/14819 is now ready for > > > > review. > > > > > > > > The changes in the PR now use GitHub Actions Artifacts for sharing > > > > binary files (such as docker images) between the build steps. This > > > > saves a lot of GitHub Actions VM resources since the docker images are > > > > built once and shared in downstream jobs. > > > > GitHub Actions Artifacts are meant to be used for sharing data between > > > > the jobs in a GitHub Actions workflow [1]. > > > > > > > > I'm looking forward to your review and feedback on > > > > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > BR, > > > > > > > > -Lari > > > > > > > > References: > > > > [1] GitHub Actions: Storing workflow data as artifacts - > > > > https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts > > > > > > > > On 2022/03/23 10:46:10 Lari Hotari wrote: > > > > > I have submitted the PR for refactoring the apache/pulsar GitHub > > > > > Actions based CI. Please review > > > > > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > > > BR, > > > > > -Lari > > > > > > > > > > On 2022/03/22 13:38:36 Enrico Olivelli wrote: > > > > > > Lari, > > > > > > > > > > > > Il Mar 22 Mar 2022, 14:32 Lari Hotari ha > > > > > > scritto: > > > > > > > > > > > > > I have resumed work to improve our GitHub Actions based Pulsar CI. > > > > > > > > > > > > > > Last year, I worked on a proof-of-concept which significantly > > > > > > > reduced the > > > > > > > resource consumption and improved the usability of the build by > > > > > > > combining > > > > > > > multiple workflows into a single larger workflow. > > > > > > > > > > > > > > The showstopper a year ago was the lack of being able to re-run a > > > > > > > single > > > > > > > failed job in a larger workflow. > > > > > > > GitHub has since then delivered this feature and no showstoppers > > > > > > > are > > > > > > > present. > > > > > > > > > > > > > > I have been posting updates to > > > > > > > https://github.com/apache/pulsar/issues/14401 "Speed up CI > > > > > > > workflows" > > > > > > > about the progress. > > > > > > > I have rebased the changes from last year's PoC, and I'm > > > > > > > finalizing and > > > > > > > testing the changes in my fork under > > > > > > > https://github.com/lhotari/pulsar/pull/59 . I'll send a PR to > > > > > > > apache/pulsar, when the refactoring is ready. > > > > > > > > > > > > > > > > > > > This is great news ! > > > > > > > > > > > > Looking
Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"
The refactored Pulsar CI workflow PR https://github.com/apache/pulsar/pull/14819 has been merged. It unblocks CI and makes it work again. Pulsar SQL integration tests are disabled temporarily until https://github.com/apache/pulsar/issues/14951 has been addressed. Please rebase your PR or close/reopen it to pick up changes for the new Pulsar CI workflow. That is necessary so that PRs can be merged. -Lari On 2022/03/30 14:08:17 Lari Hotari wrote: > > Merging the PR is blocked by https://github.com/apache/pulsar/issues/14951 . > > Pulsar SQL doesn't work with Java 11.0.14.1 version. It fails with this error > message: > Exception in thread "main" java.lang.IllegalArgumentException: Cannot parse > version 11.0.14.1 > at io.prestosql.server.JavaVersion.parse(JavaVersion.java:76) > at > io.prestosql.server.PrestoSystemRequirements.verifyJavaVersion(PrestoSystemRequirements.java:102) > at > io.prestosql.server.PrestoSystemRequirements.verifyJvmRequirements(PrestoSystemRequirements.java:45) > at io.prestosql.server.PrestoServer.run(PrestoServer.java:78) > at io.prestosql.$gen.Presto_33220220330_100314_1.run(Unknown Source) > at io.prestosql.server.PrestoServer.main(PrestoServer.java:72) > > I'll apply a workaround to unblock CI. > > -Lari > > On 2022/03/30 06:52:38 Lari Hotari wrote: > > Thank you for the reviews and feedback. I have started making the switch to > > the new refactored Pulsar CI. > > > > Merging new PRs are blocked until the switch is ready. The reason for this > > is that I have merged https://github.com/apache/pulsar/pull/14939 preparing > > for merging https://github.com/apache/pulsar/pull/14819 . > > > > The GitHub Actions "required checks" change in the refactored Pulsar CI and > > there can be only one effective set of "required checks" for a branch. > > > > After the new Pulsar CI workflow PR has been merged, each in-progress PR > > has to be closed & immediately reopened to pick up the new workflow and the > > PR build has to run through the new workflow. Another way to pick up the > > new workflow is to rebase the PR (or merge master branch changes to it). > > > > Please let me know if you experience any issues with the new Pulsar CI > > workflow. I'll be on the #testing channel on Pulsar Slack too. > > > > -Lari > > > > On 2022/03/29 15:43:31 Michael Marshall wrote: > > > Great work, Lari! It's great news that GitHub's new feature helps this > > > valuable work move forward. I look forward to seeing your PR merged, > > > and I am happy to help resolve any issues that might pop up. > > > > > > Thanks, > > > Michael > > > > > > On Tue, Mar 29, 2022 at 7:55 AM Lari Hotari wrote: > > > > > > > > The PR has sufficient reviews, and I'll proceed with merging it today > > > > or tomorrow. > > > > Please provide feedback now if you want to do that before the PR is > > > > merged. > > > > > > > > Thanks! > > > > > > > > -Lari > > > > > > > > On 2022/03/28 20:05:14 Lari Hotari wrote: > > > > > The PR https://github.com/apache/pulsar/pull/14819 is now ready for > > > > > review. > > > > > > > > > > The changes in the PR now use GitHub Actions Artifacts for sharing > > > > > binary files (such as docker images) between the build steps. This > > > > > saves a lot of GitHub Actions VM resources since the docker images > > > > > are built once and shared in downstream jobs. > > > > > GitHub Actions Artifacts are meant to be used for sharing data > > > > > between the jobs in a GitHub Actions workflow [1]. > > > > > > > > > > I'm looking forward to your review and feedback on > > > > > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > > > BR, > > > > > > > > > > -Lari > > > > > > > > > > References: > > > > > [1] GitHub Actions: Storing workflow data as artifacts - > > > > > https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts > > > > > > > > > > On 2022/03/23 10:46:10 Lari Hotari wrote: > > > > > > I have submitted the PR for refactoring the apache/pulsar GitHub > > > > > > Actions based CI. Please review > > > > > > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > > > > > BR, > > > > > > -Lari > > > > > > > > > > > > On 2022/03/22 13:38:36 Enrico Olivelli wrote: > > > > > > > Lari, > > > > > > > > > > > > > > Il Mar 22 Mar 2022, 14:32 Lari Hotari ha > > > > > > > scritto: > > > > > > > > > > > > > > > I have resumed work to improve our GitHub Actions based Pulsar > > > > > > > > CI. > > > > > > > > > > > > > > > > Last year, I worked on a proof-of-concept which significantly > > > > > > > > reduced the > > > > > > > > resource consumption and improved the usability of the build by > > > > > > > > combining > > > > > > > > multiple workflows into a single larger workflow. > > > > > > > > > > > > > > > > The showstopper a year ago was the lack of being able to re-run > > > > > > > > a single > > > > > > > > failed job in a larger workflow. > > > > > > > > G
Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"
Lari, I would start a new thread with an 'Heads up' People may not follow this long thread and miss this piece of information Great work! Thank you very much Enrico Il Mer 30 Mar 2022, 18:32 Lari Hotari ha scritto: > The refactored Pulsar CI workflow PR > https://github.com/apache/pulsar/pull/14819 has been merged. It unblocks > CI and makes it work again. Pulsar SQL integration tests are disabled > temporarily until https://github.com/apache/pulsar/issues/14951 has been > addressed. > > Please rebase your PR or close/reopen it to pick up changes for the new > Pulsar CI workflow. That is necessary so that PRs can be merged. > > -Lari > > > On 2022/03/30 14:08:17 Lari Hotari wrote: > > > > Merging the PR is blocked by > https://github.com/apache/pulsar/issues/14951 . > > > > Pulsar SQL doesn't work with Java 11.0.14.1 version. It fails with this > error message: > > Exception in thread "main" java.lang.IllegalArgumentException: Cannot > parse version 11.0.14.1 > > at io.prestosql.server.JavaVersion.parse(JavaVersion.java:76) > > at > io.prestosql.server.PrestoSystemRequirements.verifyJavaVersion(PrestoSystemRequirements.java:102) > > at > io.prestosql.server.PrestoSystemRequirements.verifyJvmRequirements(PrestoSystemRequirements.java:45) > > at io.prestosql.server.PrestoServer.run(PrestoServer.java:78) > > at io.prestosql.$gen.Presto_33220220330_100314_1.run(Unknown > Source) > > at io.prestosql.server.PrestoServer.main(PrestoServer.java:72) > > > > I'll apply a workaround to unblock CI. > > > > -Lari > > > > On 2022/03/30 06:52:38 Lari Hotari wrote: > > > Thank you for the reviews and feedback. I have started making the > switch to the new refactored Pulsar CI. > > > > > > Merging new PRs are blocked until the switch is ready. The reason for > this is that I have merged https://github.com/apache/pulsar/pull/14939 > preparing for merging https://github.com/apache/pulsar/pull/14819 . > > > > > > The GitHub Actions "required checks" change in the refactored Pulsar > CI and there can be only one effective set of "required checks" for a > branch. > > > > > > After the new Pulsar CI workflow PR has been merged, each in-progress > PR has to be closed & immediately reopened to pick up the new workflow and > the PR build has to run through the new workflow. Another way to pick up > the new workflow is to rebase the PR (or merge master branch changes to it). > > > > > > Please let me know if you experience any issues with the new Pulsar CI > workflow. I'll be on the #testing channel on Pulsar Slack too. > > > > > > -Lari > > > > > > On 2022/03/29 15:43:31 Michael Marshall wrote: > > > > Great work, Lari! It's great news that GitHub's new feature helps > this > > > > valuable work move forward. I look forward to seeing your PR merged, > > > > and I am happy to help resolve any issues that might pop up. > > > > > > > > Thanks, > > > > Michael > > > > > > > > On Tue, Mar 29, 2022 at 7:55 AM Lari Hotari > wrote: > > > > > > > > > > The PR has sufficient reviews, and I'll proceed with merging it > today or tomorrow. > > > > > Please provide feedback now if you want to do that before the PR > is merged. > > > > > > > > > > Thanks! > > > > > > > > > > -Lari > > > > > > > > > > On 2022/03/28 20:05:14 Lari Hotari wrote: > > > > > > The PR https://github.com/apache/pulsar/pull/14819 is now ready > for review. > > > > > > > > > > > > The changes in the PR now use GitHub Actions Artifacts for > sharing binary files (such as docker images) between the build steps. This > saves a lot of GitHub Actions VM resources since the docker images are > built once and shared in downstream jobs. > > > > > > GitHub Actions Artifacts are meant to be used for sharing data > between the jobs in a GitHub Actions workflow [1]. > > > > > > > > > > > > I'm looking forward to your review and feedback on > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > > > > > BR, > > > > > > > > > > > > -Lari > > > > > > > > > > > > References: > > > > > > [1] GitHub Actions: Storing workflow data as artifacts - > https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts > > > > > > > > > > > > On 2022/03/23 10:46:10 Lari Hotari wrote: > > > > > > > I have submitted the PR for refactoring the apache/pulsar > GitHub Actions based CI. Please review > https://github.com/apache/pulsar/pull/14819 . > > > > > > > > > > > > > > BR, > > > > > > > -Lari > > > > > > > > > > > > > > On 2022/03/22 13:38:36 Enrico Olivelli wrote: > > > > > > > > Lari, > > > > > > > > > > > > > > > > Il Mar 22 Mar 2022, 14:32 Lari Hotari > ha scritto: > > > > > > > > > > > > > > > > > I have resumed work to improve our GitHub Actions based > Pulsar CI. > > > > > > > > > > > > > > > > > > Last year, I worked on a proof-of-concept which > significantly reduced the > > > > > > > > > resource consumption and improved the usability of the > build by combining > > > > > > > > > multiple workflows into a single la
Fwd: Call for Presentations now open, ApacheCon North America 2022
The Call For Presentations for ApacheCon NA in New Orleans is now open. There will be a Pulsar Event Streaming track. Please consider attending and submitting a talk. This will be an in-person conference only. Further details will come as we get closer to the event. All The Best, Dave > Begin forwarded message: > > From: Rich Bowen > Subject: Call for Presentations now open, ApacheCon North America 2022 > Date: March 30, 2022 at 5:16:06 AM PDT > To: annou...@apachecon.com > > [You are receiving this because you are subscribed to one or more user > or dev mailing list of an Apache Software Foundation project.] > > ApacheCon draws participants at all levels to explore “Tomorrow’s > Technology Today” across 300+ Apache projects and their diverse > communities. ApacheCon showcases the latest developments in ubiquitous > Apache projects and emerging innovations through hands-on sessions, > keynotes, real-world case studies, trainings, hackathons, community > events, and more. > > The Apache Software Foundation will be holding ApacheCon North America > 2022 at the New Orleans Sheration, October 3rd through 6th, 2022. The > Call for Presentations is now open, and will close at 00:01 UTC on May > 23rd, 2022. > > We are accepting presentation proposals for any topic that is related > to the Apache mission of producing free software for the public good. > This includes, but is not limited to: > > Community > Big Data > Search > IoT > Cloud > Fintech > Pulsar > Tomcat > > You can submit your session proposals starting today at > https://cfp.apachecon.com/ > > Rich Bowen, on behalf of the ApacheCon Planners > apachecon.com > @apachecon
Re: [DISCUSS] Proceeding with PIP-62 plan, before Apache Pulsar 2.10.0 is released
Is there a plan to make progress with the Trino PR https://github.com/trinodb/trino/pull/8020 which would replace Pulsar SQL? Pulsar SQL is not compatibile with Java 11.0.14.1 since Presto 332 fails to parse this type of version string. That issue is reported as https://github.com/apache/pulsar/issues/14951 . The PR to fix that is https://github.com/apache/pulsar/pull/14953 . Presto 334 removes the Java version parser class completely and therefore it fixes the issue. Presto 334 requires Java 11 from what I've heard so merging this PR would drop support for Java 8 in Pulsar SQL. I would assume that it's fine for doing this in the master branch. Are there any ideas how to resolve https://github.com/apache/pulsar/issues/14951 in some other way? BR, Lari On 2021/12/23 08:42:57 Lari Hotari wrote: > > I believe we want to keep SQL until the code change lands in Trino. > Because > there are still users using this component. > > There have been multiple public dev@pulsar.apache.org discussions about > PIP-62 which was initialized in April 2020. > Those users using Pulsar SQL can keep on using Pulsar 2.8.x or 2.9.x until > the feature is available in Trino. Isn't that a viable option? > > The Pulsar community is here to help with the work. What is the status of > Trino work? Are there tasks that need help? Is there any ETA for the > landing of code in Trino? > Could we resolve this together? > > BR, Lari > > On Thu, Dec 23, 2021 at 2:39 AM Sijie Guo wrote: > > > Sorry. When you say "we discussed", who are "we"? Is it DataStax? > > > > I believe we want to keep SQL until the code change lands in Trino. Because > > there are still users using this component. > > > > - Sijie > > > > On Tue, Dec 21, 2021 at 11:34 PM Enrico Olivelli > > wrote: > > > > > Lari, > > > > > > Il giorno mer 22 dic 2021 alle ore 08:31 Lari Hotari > > > > > ha scritto: > > > > > > > Dear Pulsar community members, > > > > > > > > PIP-62[1], "PIP 62: Move connectors, adapters and Pulsar Presto to > > > separate > > > > repositories" was created in April 2020. The repositories for > > > > pulsar-connectors, pulsar-adapters and pulsar-sql were created about a > > > year > > > > ago [2]. > > > > > > > > I'd like to propose that we continue with the PIP-62 plan asap, before > > > > Apache Pulsar 2.10.0 is released. > > > > > > > > I'm also suggesting that we drop Pulsar SQL from apache/pulsar without > > > > waiting for the Trino Pulsar PR [3] being completed. > > > > > > > > I am volunteering to making the changes as per the PIP-62 plan. > > > > When can we proceed with the plan? Do we need an explicit vote on the > > > > mailing list about this? > > > > > > > > > > We discussed this many times in the past year. > > > I believe that there is no need to wait > > > > > > Enrico > > > > > > > > > > > > > > > > > BR, > > > > > > > > Lari > > > > > > > > [1] > > > > > > > > > > > > > https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories > > > > [2] > > > > > > > > > > > > > https://lists.apache.org/thread.html/r9e6ec742e2896da1f0ce7d4adc7cb84fc6db6dbf797732ccdd50fb86%40%3Cdev.pulsar.apache.org%3E > > > > [3] https://github.com/trinodb/trino/pull/8020 > > > > > > > > Other email threads: > > > > * [Discuss] Don't include presto/trino in the normal Pulsar > > distribution > > > - > > > > https://lists.apache.org/thread/jn96tct54mn0tvdot62vdslrvs38fm6d > > > > * Updates on Presto connector for PIP-62 - > > > > https://lists.apache.org/thread/f9n6sc2mrboq5sxhjbr7gvdl8vqp9fpk > > > > > > > > > >
[discuss] Pulsar Community Meetings- should the times change? Where are the recordings?
Hello all, We currently have two Pulsar community meetings that happen every other week. They are on Tuesdays 4 pm (16:00) Pacific Time and Thursdays 8:30 am (08:30) Pacific. The one on Tuesdays seems to be poorly attended, with only one or two people attending. The Thursday one is better attended but seems to have the same people. I was wondering if we should change the Tuesday meeting to something later so that it might better cover the APJ time zones or maybe earlier so that people on the east coast of the US wouldn't have the meeting during dinner time. Thoughts? Preferences? Also, I would like to watch the recordings when I am not able to attend, where are the previous ones stored? I looked through the website at pulsar.apache.org and am having a tough time finding them. BTW if you don't know about the community meetings, they are technical meetings where members get on a zoom call to discuss Pulsar. If you want to join, go here: https://pulsar.apache.org/en/events/ and you will see the calendar. And Michael Marshall has been doing a great job of taking meeting minutes and you can find those on the mailing list archive ( https://lists.apache.org/list.html?dev@pulsar.apache.org) Thanks, Aaron Williams
[GitHub] [pulsar-client-node] liutt1312 opened a new issue #206: About pulsar-client-cpp cmake
liutt1312 opened a new issue #206: URL: https://github.com/apache/pulsar-client-node/issues/206 Please set them or make sure they are set and tested correctly in the CMake files: GMOCK_INCLUDE_PATH used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/lib used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/examples used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/tests used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python used as include directory in directory /home/liutt/Downloads/pulsar/pulsar-client-cpp/python -- Configuring incomplete, errors occurred! See also "/home/liutt/Downloads/pulsar/pulsar-client-cpp/CMakeFiles/CMakeOutput.log". See also "/home/liutt/Downloads/pulsar/pulsar-client-cpp/CMakeFiles/CMakeError.log". -- This is an aut
[GitHub] [pulsar-client-node] liutt1312 closed issue #206: About pulsar-client-cpp cmake
liutt1312 closed issue #206: URL: https://github.com/apache/pulsar-client-node/issues/206 -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-client-node] liutt1312 opened a new issue #207: About cmake pulsar-client-cpp
liutt1312 opened a new issue #207:
URL: https://github.com/apache/pulsar-client-node/issues/207
clang-tidy found at /usr/bin/clang-tidy
clang-format not found
CMake Error: The following variables are used in this project, but they are
set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake
files:
GMOCK_INCLUDE_PATH
used as include directory in directory
/home/liutt/Downloads/pulsar/pulsar-client-cpp
...
-- Configuring incomplete, errors occurred!
See also
"/home/liutt/Downloads/pulsar/pulsar-client-cpp/CMakeFiles/CMakeOutput.log".
See also
"/home/liutt/Downloads/pulsar/pulsar-client-cpp/CMakeFiles/CMakeError.log".
CMakeError.log:
Linking C executable cmTC_aa1c4
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_aa1c4.dir/link.txt
--verbose=1
/usr/bin/cc -DCMAKE_HAVE_LIBC_PTHREADCMakeFiles/cmTC_aa1c4.dir/src.c.o
-o cmTC_aa1c4
/usr/bin/ld: CMakeFiles/cmTC_aa1c4.dir/src.c.o: in function `main':
src.c:(.text+0x46): undefined reference to `pthread_create'
/usr/bin/ld: src.c:(.text+0x52): undefined reference to `pthread_detach'
/usr/bin/ld: src.c:(.text+0x63): undefined reference to `pthread_join'
collect2: error: ld returned 1 exit status
make[1]: *** [CMakeFiles/cmTC_aa1c4.dir/build.make:87：cmTC_aa1c4] 错误 1
make[1]:
离开目录“/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp”
make: *** [Makefile:121：cmTC_aa1c4/fast] 错误 2
Source file was:
#include
void* test_func(void* data)
{
return data;
}
int main(void)
{
pthread_t thread;
pthread_create(&thread, NULL, test_func, NULL);
pthread_detach(thread);
pthread_join(thread, NULL);
pthread_atfork(NULL, NULL, NULL);
pthread_exit(NULL);
return 0;
}
Determining if the getauxval exist failed with the following output:
Change Dir:
/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/make cmTC_b8f12/fast && /usr/bin/make -f
CMakeFiles/cmTC_b8f12.dir/build.make CMakeFiles/cmTC_b8f12.dir/build
make[1]:
进入目录“/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp”
Building CXX object CMakeFiles/cmTC_b8f12.dir/CheckSymbolExists.cxx.o
/usr/bin/c++-D_PULSAR_VERSION_INTERNAL_=\"\" -fPIE -o
CMakeFiles/cmTC_b8f12.dir/CheckSymbolExists.cxx.o -c
/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:2:10:
fatal error: auvx.h: 没有那个文件或目录
2 | #include
| ^~~~
compilation terminated.
make[1]: ***
[CMakeFiles/cmTC_b8f12.dir/build.make:66：CMakeFiles/cmTC_b8f12.dir/CheckSymbolExists.cxx.o]
错误 1
make[1]:
离开目录“/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp”
make: *** [Makefile:121：cmTC_b8f12/fast] 错误 2
File
/home/liutt/Downloads/pulsar/pulsar-client-cpp/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
/* */
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef getauxval
return ((int*)(&getauxval))[argc];
#else
(void)argc;
return 0;
#endif
}
--
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...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace opened a new pull request #39: fix: some link click fail
urfreespace opened a new pull request #39: URL: https://github.com/apache/pulsar-site/pull/39 Signed-off-by: Li Li -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace merged pull request #39: fix: some link click fail
urfreespace merged pull request #39: URL: https://github.com/apache/pulsar-site/pull/39 -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace opened a new pull request #40: [WIP]feat: add versions dropdown menu in docs page
urfreespace opened a new pull request #40: URL: https://github.com/apache/pulsar-site/pull/40 Signed-off-by: Li Li -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
