[GitHub] [pulsar-test-infra] nodece commented on issue #59: [docbot] Cannot to label for PR correctly
nodece commented on issue #59: URL: https://github.com/apache/pulsar-test-infra/issues/59#issuecomment-1229156514 Met again: ``` [INFO] 2022/08/27 08:45:24 @List issue labels [INFO] 2022/08/27 08:45:24 Issue labels: [type/improvement component/security release/2.9.4 release/2.11.1 release/2.10.3] [INFO] 2022/08/27 08:45:24 @List current labels [INFO] 2022/08/27 08:45:24 Current labels: [] [INFO] 2022/08/27 08:45:24 @List expected labels [INFO] 2022/08/27 08:45:24 Expected labels: map[doc-not-needed:true] [INFO] 2022/08/27 08:45:24 Labels to remove: map[] [INFO] 2022/08/27 08:45:24 @Add missing label [FATAL] 2022/08/27 08:45:25 /home/runner/work/pulsar/pulsar/docbot/main.go:630: Please provide a correct documentation label for your PR. Instructions see [Pulsar Documentation Label Guide](https://docs.google.com/document/d/1Qw7LHQdXWBW9t2-r-A7QdFDBwmZh6ytB4guwMoXHqc0). ``` https://github.com/apache/pulsar/pull/16815 -- 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] Anonymitaet created a discussion: Pulsar Release Timeline Page Design
GitHub user Anonymitaet created a discussion: Pulsar Release Timeline Page Design Hi team, Currently, we do not have a place showing the timeline for all Pulsar releases. How about creating a Pulsar [Release Notes > Timeline](https://pulsar.apache.org/release-notes/timeline) page along with the following content? 1. Add the [Pulsar release timeline table](https://docs.google.com/spreadsheets/d/1XHmzno-1kbHvPp7eogri8XAiShH-EgpEG40svte-qxM/edit#gid=1677243891) as below. https://user-images.githubusercontent.com/50226895/187023651-f6d5303d-a864-45b0-89c3-095e8cab2a47.png";> 2. The timeline table should be updated automatically. Data (release date + release manager) can be pulled from https://github.com/apache/pulsar/releases. 3. [Versions page](https://pulsar.apache.org/versions) info is consolidated into the timeline page, so the Versions page can be removed. GitHub link: https://github.com/apache/pulsar/discussions/17310 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] Anonymitaet added a comment to the discussion: Pulsar Release Timeline Page Design
GitHub user Anonymitaet added a comment to the discussion: Pulsar Release Timeline Page Design @tisonkun @urfreespace @SignorMercurio thoughts? GitHub link: https://github.com/apache/pulsar/discussions/17310#discussioncomment-3488620 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] Anonymitaet deleted a comment on the discussion: Pulsar Release Timeline Page Design
GitHub user Anonymitaet deleted a comment on the discussion: Pulsar Release Timeline Page Design @tisonkun @urfreespace @SignorMercurio thoughts? GitHub link: https://github.com/apache/pulsar/discussions/17310#discussioncomment-3488620 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] Anonymitaet edited a discussion: Pulsar Release Timeline Page Design
GitHub user Anonymitaet edited a discussion: Pulsar Release Timeline Page Design Hi team, Currently, we do not have a place showing the timeline for all Pulsar releases. How about creating a Pulsar [Release Notes > Timeline](https://pulsar.apache.org/release-notes/timeline) page along with the following content? 1. Add the [Pulsar release timeline table](https://docs.google.com/spreadsheets/d/1XHmzno-1kbHvPp7eogri8XAiShH-EgpEG40svte-qxM/edit#gid=1677243891) as below. https://user-images.githubusercontent.com/50226895/187023651-f6d5303d-a864-45b0-89c3-095e8cab2a47.png";> 2. The timeline table should be updated automatically. Data (release date + release manager) can be pulled from https://github.com/apache/pulsar/releases. 3. [Versions page](https://pulsar.apache.org/versions) info is consolidated into the timeline page, so the Versions page can be removed. ☘️☘️☘️ Hi @tisonkun @urfreespace @SignorMercurio thoughts? GitHub link: https://github.com/apache/pulsar/discussions/17310 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] SignorMercurio added a comment to the discussion: Pulsar Release Timeline Page Design
GitHub user SignorMercurio added a comment to the discussion: Pulsar Release Timeline Page Design Looks great, though not clear on how to update the table from releases. GitHub link: https://github.com/apache/pulsar/discussions/17310#discussioncomment-3488628 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
Re: Pulsar CI congested, master branch build broken
Hi, Lari Thanks for bringing this to our attention! I was wondering if we could consider using the self-hosted runner? As there are currently more than 2k projects in one apache org. Best, Max Xu On Fri, Aug 26, 2022 at 8:00 PM Lari Hotari wrote: > Hi, > > GitHub Actions builds have been piling up in the build queue in the last > few days. > I posted on bui...@apache.org > https://lists.apache.org/thread/6lbqr0f6mqt9s8ggollp5kj2nv7rlo9s and > created INFRA ticket https://issues.apache.org/jira/browse/INFRA-23633 > about this issue. > There's also a thread on the-asf slack, > https://the-asf.slack.com/archives/CBX4TSBQ8/p1661512133913279 . > > It seems that our build queue is finally getting picked up, but it would > be great to see if we hit quota and whether that is the cause of pauses. > > Another issue is that the master branch broke after merging 2 conflicting > PRs. > The fix is in https://github.com/apache/pulsar/pull/17300 . > > Merging PRs will be slow until we have these 2 problems solved and > existing PRs rebased over the changes. Let's prioritize merging #17300 > before pushing more changes. > > I'd like to point out that a good way to get build feedback before sending > a PR, is to run builds on your personal GitHub Actions CI. The benefit of > this is that it doesn't consume the shared quota and builds usually start > instantly. > There are instructions in the contributors guide about this. > https://pulsar.apache.org/contributing/#ci-testing-in-your-fork > You simply open PRs to your own fork of apache/pulsar to run builds on > your personal GitHub Actions CI. > > BR, > > Lari > > > > > > > >
Re: Pulsar CI congested, master branch build broken
And +1 vote for "Provide information about GitHub Actions usage for apache organization", which would be greatly helpful by making these information transparency. Best, Max Xu On Fri, Aug 26, 2022 at 8:00 PM Lari Hotari wrote: > Hi, > > GitHub Actions builds have been piling up in the build queue in the last > few days. > I posted on bui...@apache.org > https://lists.apache.org/thread/6lbqr0f6mqt9s8ggollp5kj2nv7rlo9s and > created INFRA ticket https://issues.apache.org/jira/browse/INFRA-23633 > about this issue. > There's also a thread on the-asf slack, > https://the-asf.slack.com/archives/CBX4TSBQ8/p1661512133913279 . > > It seems that our build queue is finally getting picked up, but it would > be great to see if we hit quota and whether that is the cause of pauses. > > Another issue is that the master branch broke after merging 2 conflicting > PRs. > The fix is in https://github.com/apache/pulsar/pull/17300 . > > Merging PRs will be slow until we have these 2 problems solved and > existing PRs rebased over the changes. Let's prioritize merging #17300 > before pushing more changes. > > I'd like to point out that a good way to get build feedback before sending > a PR, is to run builds on your personal GitHub Actions CI. The benefit of > this is that it doesn't consume the shared quota and builds usually start > instantly. > There are instructions in the contributors guide about this. > https://pulsar.apache.org/contributing/#ci-testing-in-your-fork > You simply open PRs to your own fork of apache/pulsar to run builds on > your personal GitHub Actions CI. > > BR, > > Lari > > > > > > > >
Re: [DISCUSS] Use Github project to track the multi clients development
Reviewed and left a comment: the actions/add-to-project says itself does not support the Classic GitHub Project. [1] We may need to be aware of this. [1] https://github.com/actions/add-to-project#actionsadd-to-project Best, Max Xu On Thu, Aug 25, 2022 at 7:43 PM Zike Yang wrote: > > I think that the main problem is that in our community we have plenty > of Java developers and there are a few committers that review > the patches on non-Java client. > > Yes. The primary purpose of this project is to keep track of many > uncaught-up features of other languages clients. And there will be a > lot of features that we need to develop. > > If there is no objection, please help review and merge this PR: > https://github.com/apache/pulsar/pull/17201 Thanks. > > > Best, > Zike Yang > > On Wed, Aug 24, 2022 at 9:20 PM Enrico Olivelli > wrote: > > > > I think that the main problem is that in our community we have plenty > > of Java developers and there are a few committers that review > > the patches on non-Java client. > > The same problem is also for other projects like the Helm Chart. > > Also, the Java client is used internally by the broker so it is > > usually more used and it needs more work > > > > That said I agree that with the proposal in this thread > > > > Enrico > > > > Il giorno mer 24 ago 2022 alle ore 14:32 Qiang Huang > > ha scritto: > > > > > > It makes sense to me. I'm thinking, if an issue is encountered in a > Java > > > client, it is possible to be in other clients. If so, the Java client > board > > > is also needed. > > > > > > mattison chao 于2022年8月22日周一 16:00写道： > > > > > > > +1 > > > > > > > > Best, > > > > Mattison > > > > > > > > On Mon, 22 Aug 2022 at 15:52, Baodi Shi > > > > > wrote: > > > > > > > > > Nice idea! > > > > > > > > > > Thanks, > > > > > Baodi Shi > > > > > > > > > > > On Aug 22, 2022, at 12:4250, Zike Yang wrote: > > > > > > > > > > > > Hi, all > > > > > > > > > > > > Currently, many features or bug fixes of some clients like the > C++ > > > > > > client and Python client have not caught up with the Java > client. For > > > > > > better tracking of these features or bug fixes, I have created a > > > > > > Github project called `Apache Pulsar / Multi Clients`[0] under > the > > > > > > pulsar main repo. It can be removed if we don't like it this way. > > > > > > > > > > > > There are six columns in this Github project: > > > > > > * Backlog: Low priority issues or issues(or cards) that have not > been > > > > > > initially investigated. > > > > > > * Todo: Newly added issues and issues suitable for contributors > to pick > > > > > first. > > > > > > * In progress: Work in progress issues or PRs. > > > > > > * Review in progress: The PRs or issues that are waiting for > review. > > > > > > * Reviewer approved: The PRs or issues that are waiting to merge. > > > > > > * Done: Merged PRs and Solved issues. > > > > > > > > > > > > This not only helps to track the status of other clients' > features and > > > > > > bug fixes but also helps contributors who want to participate in > other > > > > > > language client feature development to pick the task. > > > > > > > > > > > > This Project is currently only for clients maintained by the main > > > > > > pulsar repository, such as C++ and Python clients. > > > > > > > > > > > > I have created a PR [1] to add C++ and Python client issues and > PRs to > > > > > > the Multi Clients project. > > > > > > > > > > > > Please let me know what you think. Thanks! > > > > > > > > > > > > [0] https://github.com/apache/pulsar/projects/12 > > > > > > [1] https://github.com/apache/pulsar/pull/17201 > > > > > > > > > > > > Best, > > > > > > Zike Yang > > > > > > > > > > > > > > > > > > > > > > > -- > > > BR, > > > Qiang Huang >
Re: [VOTE] Pulsar Release 2.7.5 Candidate 3
+1(non-binding) - Checked signatures/checksums - Checked the license headers - Ran the standalone - Validate Connectors - Validate Pub/Sub and Java Functions - Validate Stateful Functions Haiting Jiang 于2022年8月27日周六 06:40写道： > This is the third release candidate for Apache Pulsar, version 2.7.5. > > It fixes the following issues: > https://github.com/apache/pulsar/compare/v2.7.4...v2.7.5-candidate-3 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.7.5-candidate-3/ > > SHA-512 checksums: > > > 6aa74cb742c411edd40de2199eb70d774d0ce8cb7dbfc2ce33fce7e87949aafa73f93a1e154261b58a1df4ad10160bf43fc5a93b1aa9a0466fcf2a3ba1a6e385 > apache-pulsar-2.7.5-bin.tar.gz > > facb1698e394b5428a0b9b6d71b891013f3c5b473cf72dd68a75ca729800710f2c6c476b1c47f7804c1b1c0941f79a6a9f334c7c703f66f6bac8f399386c5ad6 > apache-pulsar-2.7.5-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1172/ > > The tag to be voted upon: > v2.7.5-candidate-3 (8eae5b8d572861e49c40d456b1f3cbc5d414afe1) > https://github.com/apache/pulsar/releases/tag/v2.7.5-candidate-3 > > Docker images: > > > https://hub.docker.com/layers/jason918/pulsar/2.7.5/images/sha256-ec77603bd943f1a56065d155428d6edccb2bf2ec57fafab8112c4b73c7bfcb6e > > https://hub.docker.com/layers/pulsar-all/jason918/pulsar-all/latest/images/sha256-0792a0ec75ecbc16c9a42af127a68b3dea2331be3f2f0599f5fb1f4cd78def25 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > Thanks, > Haiting > -- BR, Qiang Huang
[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #184: Migrate all docs from /tools to /reference
SignorMercurio opened a new pull request, #184: URL: https://github.com/apache/pulsar-site/pull/184 No longer uses `pulsar*-md.sh` and brodocs because there's no need to generate HTML files. Meanwhile, add separate sidebars for each component and a global navbar to navigate between these components. @urfreespace PTAL -- 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
