[GitHub] [pulsar-site] urfreespace merged pull request #57: feat: blogs sync migrate and some links broken fix

[GitBox]

urfreespace merged PR #57:
URL: https://github.com/apache/pulsar-site/pull/57


-- 
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-test-infra] lhotari opened a new pull request, #34: [pulsarbot] Address issue where pulsarbot exits too early

[GitBox]

lhotari opened a new pull request, #34:
URL: https://github.com/apache/pulsar-test-infra/pull/34

   - `set -e` mode sometimes behaves in unexpected ways
  explanation:
  http://mywiki.wooledge.org/BashFAQ/105
 - in this case, the real culprit was the counter
   `((foundjobs++))` which made the script exit


-- 
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-test-infra] lhotari commented on pull request #34: [pulsarbot] Address issue where pulsarbot exits too early

[GitBox]

lhotari commented on PR #34:
URL: https://github.com/apache/pulsar-test-infra/pull/34#issuecomment-1106588964

   I'm merging to fix "/pulsarbot rerun-failure-checks". Please do post-merge 
review.


-- 
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-test-infra] lhotari merged pull request #34: [pulsarbot] Address issue where pulsarbot exits too early

[GitBox]

lhotari merged PR #34:
URL: https://github.com/apache/pulsar-test-infra/pull/34


-- 
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-test-infra] lhotari commented on pull request #34: [pulsarbot] Address issue where pulsarbot exits too early

[GitBox]

lhotari commented on PR #34:
URL: https://github.com/apache/pulsar-test-infra/pull/34#issuecomment-1106590927

   This was a follow up change to #33


-- 
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: Re-running failed flaky builds in refactored Pulsar CI GitHub Actions workflow

[Lari Hotari]

Unfortunately, the previous change had issues restarting more than 1 build job.
The problem has been resolved now. The change was 
https://github.com/apache/pulsar-test-infra/pull/34 . I merged the change, so 
please do post-merge reviews.

"/pulsarbot rerun-failure-checks" should work now. I'm sorry for the 
inconvenience that it caused when it wasn't working for all cases. Please let 
me know if there are any remaining issues.

-Lari

On 2022/04/21 09:45:37 Lari Hotari wrote:
> I have made a fix to the problem described below.
> Please review https://github.com/apache/pulsar-test-infra/pull/33 .
> 
> After this change is merged, closing and reopening PRs could be used to pick 
> up most recent change from the master branch and "/pulsarbot 
> rerun-failure-checks" will be able to rerun the failed jobs.
> 
> -Lari
> 
> On 2022/04/01 14:34:02 Lari Hotari wrote:
> > I now realized that my advice to close & reopen PRs to pick up master 
> > branch changes is problematic. This will cause issues with "/pulsarbot 
> > rerun-failure-checks". The script currently looks for the build to restart 
> > with the PR's head commit sha. If closing and reopening is used to start 
> > new PR build jobs, all build jobs will have the same head commit sha 
> > attached to them. When checking for that failed builds, the script will 
> > find also old builds with the same head commit sha and also restart them.
> > 
> > Please rebased your PR (or merge master branch changes to it) to pick up 
> > changes from master. Don't close & reopen PRs as I had advised earlier 
> > since it causes problems. The wrong builds will be run and that adds up in 
> > the build queue.
> > 
> > -Lari
> > 
> > 
> > 
> > On 2022/04/01 08:38:54 Lari Hotari wrote:
> > > Hi all,
> > > 
> > > There's a small limitation in re-running failed jobs (builds that fail 
> > > because of flaky tests) in the refactored Pulsar CI workflow which 
> > > combines multiple jobs into a single workflow.
> > > 
> > > The limitation is that you need to wait for all jobs to complete before 
> > > failed jobs can be re-run.
> > > Yesterday there was some issue with GitHub Actions and the build queue 
> > > was several hours long. When there's enough build capacity and no build 
> > > queue, the new workflow finishes in about 1 hour 20 minutes.
> > > 
> > > Re-running failed jobs can be requested by commenting "/pulsarbot 
> > > rerun-failure-checks" on the  PR. This won't do anything if one of the 
> > > jobs in the workflow is still executing.
> > > 
> > > Another confusion has been the new test reporting, which shows all test 
> > > results and test failures as checks and annotations in the GitHub UI. 
> > > 
> > > Here's an example:
> > > https://github.com/apache/pulsar/pull/14805/checks?check_run_id=5777139002
> > > 
> > > There's a limitation in GitHub Actions that the test reports get attached 
> > > to the first workflow when a PR triggers more than one workflow. We still 
> > > have multiple workflows and the test reports get attached to the "CI - 
> > > CPP, Python Tests" workflow. Failed tests will show up as red check marks 
> > > and in the case of retries, the test might have succeeded in a later 
> > > attempt, but the check shows as failed. This won't prevent merging the 
> > > PR. Please keep this small detail in mind when interpreting the build 
> > > results.
> > > 
> > > The test reports are very verbose at the moment. This is a problem when 
> > > checking the PR build results on GitHub Mobile app. I have created a PR 
> > > to reduce test reporting to GitHub Actions UI in this PR: 
> > > https://github.com/apache/pulsar/pull/14959
> > > 
> > > Please let me know if there are any other questions or problems that have 
> > > come up with the new refactored Pulsar CI GitHub Actions workflow.
> > > 
> > > -Lari
> > > 
> > 
> 

Re: Enable GitHub Discussions?

[Dave Fisher]

Hi Yu,

> On Apr 21, 2022, at 11:46 PM, Yu  wrote:
> 
> Thanks all!
> 
> I understand that we need to follow the Apache way (If it didn’t happen on
> the mailing list, it didn’t happen) to *make final decisions*, but we can
> find a better place to *discuss issues and reuse information effectively*
> [1].

Another important part of The Apache Way is to make decisions by reaching 
consensus (and avoiding votes). [3]

This discussion is not finished and this should not be a call to a vote. When a 
VOTE is called it must be clear and not buried at the bottom of a long email.

The project has been using Google Docs for collaboration. Is the real 
motivation to use GitHub Discussions instead of Google Docs?

> 
> 
> 
> # Current issues
> 
> We have a lot of work in various places, but the information is not
> organized and reused effectively.
> 
> ## Slack
> - Information is not publicly accessible. You need to upgrade to paid plans
> or else you can see just the 10,000 most recent messages.
> - Information is scattered and not categorized.

The Pulsar slack has existed since the beginning of the project. We have 6688 
subscribers to the #general and that is great.

> 
> # StackOveflow
> - Inactive. Only 24 results after searching "apachepulsar".

When I search “pulsar” I get over 500 results. This is an active channel. It’s 
a place where developers go.

> 
> # Mailing List
> - Information is scattered and not categorized.
> - User experience is terrible. Plain text format decreases email
> readability. Search function is hard to use.

The search function at lists.apache.org is hard to use, but it is powerful. In 
other projects I’ve searched for and found email from 15 years ago. The new 
monthly calendar is very powerful.

If we use GitHub Discussions then the discussion of the decision won’t be on 
the mailing list. People will write emails with links to the GitHub 
Discussions. These links will eventually get stale.

If you want to improve lists.apache.org then you can influence that here: 
d...@ponymail.apache.org. Pony Mail is an Apache Incubator podling.


> 
> 
> 
> # Why try GitHub Discussions?

> 
> Compared with the platforms above and GitHub Issue, GitHub Discussions make
> collaboration more efficient by:
> 
> # Making it easier to categorize, archive, and search information
> - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and
> Tell, etc) and labels to categorize and filter information quickly.
> - Information is permanently saved.
> - Search is easy to use.
> 
> # Providing a centralized community space for conversations and questions
> - As instructed by GitHub, we can use GitHub Discussions to *discuss
> things*, and use GitHub Issues to *catalog the work* we need to do after
> we’ve reached a decision about how to move forward.
> 
> # Boosting community engagement and encouraging people to make contributions
> - It highlights project contributors and shows Most Helpful Ranking of
> Contributors.
> - It creates a place for newcomers and non-code collaborators to
> participate in a larger community.
> 
> # Calling users' attention to important issues or events
> -  Important discussions can be pinned to home pages for easy reference.
> 
> 
> 
> Feel free to share your thoughts. This vote will be open for 72 hrs.

We are not ready to vote. While it might be good to do I cannot agree with all 
of your reasoning. If forced to vote then I am -1.

I might agree to GitHub Discussions as a replacement for GoogleDocs.

We have no power to move users away from StackOverflow. A huge number follow 
Pulsar on Slack. If it’s a matter of paying for a plan then perhaps there is a 
way. The PMC should discuss that.

All The Best,
Dave

[3] http://theapacheway.com/consensus/

> 
> Then we can ask Infra to do the needed GitHub Admin tasks if we reach a
> consensus on enabling it, thank you!
> 
> [1] http://theapacheway.com/on-list/
> 
> Anonymitaet
> 
> On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher  wrote:
> 
>> I asked Infra. GitHub Discussions are not synchronized into ASF
>> Infrastructure's GitBox. That means that there is not ability to change the
>> notification scheme to send to a mailing list.
>> 
>> Technically we can go down this path only if it is possible to set a
>> notification within GitHub. You would need to look into that and if we
>> decided to go forward we can ask Infra to do the needed GitHub Admin tasks.
>> 
>> Community wise I agree with others that we are already splitting a lot of
>> work into various places.
>> 
>> Regards,
>> Dave
>> 
>> On Apr 21, 2022, at 5:47 AM, tison  wrote:
>> 
>> You can ask for ASF INFRA to see whether there is a way to bring all
>> activities of GitHub Discussion to a mailing list. Just like development
>> activities to commits@.
>> 
>> Best,
>> tison.
>> 
>> 
>> Niclas Hedhman  于2022年4月21日周四 20:16写道：
>> 
>>> 
>>> If/when GitHub disappears, will the community suffer from missing
>>> information? If so, need to solve 

[GitHub] [pulsar-test-infra] lhotari commented on pull request #34: [pulsarbot] Address issue where pulsarbot exits too early

[GitBox]

lhotari commented on PR #34:
URL: https://github.com/apache/pulsar-test-infra/pull/34#issuecomment-1106606008

   I verified the change by restarting failed builds for a PR which had more 
than 1 failing workflow, 
https://github.com/apache/pulsar/runs/6130584084?check_suite_focus=true#step:5:15
 


-- 
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-test-infra] lhotari opened a new pull request, #35: [pulsarbot] Use gawk (gnu awk) so that CSV can be properly handled

[GitBox]

lhotari opened a new pull request, #35:
URL: https://github.com/apache/pulsar-test-infra/pull/35

   ### Motivation
   
   - previously a comma in the name caused a parsing issue
 example issue: 
https://github.com/apache/pulsar/runs/6130584084?check_suite_focus=true#step:5:11
 fails to parse `CI - CPP, Python Tests`
   
   ### Modifications
   - install gnu awk (gawk) in Dockerfile
   - use gawk's FPAT feature to parse double quoted CSV
 -  removing double quotes must be done separately for each field. 
`gsub(/"/, "")` doesn't work anymore to remove all double quotes.


-- 
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-test-infra] lhotari merged pull request #35: [pulsarbot] Use gawk (gnu awk) so that CSV can be properly handled

[GitBox]

lhotari merged PR #35:
URL: https://github.com/apache/pulsar-test-infra/pull/35


-- 
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-test-infra] lhotari commented on pull request #35: [pulsarbot] Use gawk (gnu awk) so that CSV can be properly handled

[GitBox]

lhotari commented on PR #35:
URL: https://github.com/apache/pulsar-test-infra/pull/35#issuecomment-1106638581

   Please do post-merge review. 


-- 
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: Revote: Pulsar website concepts

[Melissa Logan]

Update on the Pulsar website launch: we're getting very close.

The group in the #website channel is Slack is taking a final look at the
ecosystem and docs pages. We will soon have a launch date to share.

Thanks to all who provided input via the survey Yu shared a few weeks ago.
(1) Note: There was a Docusaurus update that caused breaking changes during
that time, so some of you noticed odd behaviors on the site which have
since been resolved. You can preview the new site here --
https://pulsar-next.staged.apache.org/ -- but keep in mind there are PRs
that haven't been committed (2) and syncing issues that will resolve.

If you see any red flags NOT already noted in the PR or weekly status doc
(3), please let us know here or on #website channel by April 29. Much
appreciated.

(1) https://lists.apache.org/thread/ndrkkcm5s8xojxsgbn8wg4j1kxj37wqj
(2) https://github.com/apache/pulsar-site/pull/53
(3)
https://docs.google.com/document/d/1QtkqXMxhF8pqfJcdkep4Wd7mm1HlQquUEkwQwHC67t8/edit#

On Fri, Dec 10, 2021 at 9:58 AM Melissa Logan  wrote:

> For record-keeping, we have added a new PIP that captures details for the
> website design/content project:
> https://github.com/apache/pulsar/issues/13235
>
> Anonymitaet, it references we'll collaborate with you and others on the
> work being done for PIP 87. I plan to start a website channel in Slack to
> aid in our collaboration.
>
> Any questions, please let me know. Thanks!
>
> Melissa
>
>
> On Wed, Nov 3, 2021 at 7:57 PM Anonymitaet _ 
> wrote:
>
>> Hi Melissa, thanks for your proposal!
>>
>> Hi community, as discussed before1, we're performing these tasks:
>>
>>- Upgrading the Pulsar website framework2. We're making progress
>>every week. You can check the details and progress here3.
>>- Designing the information architecture4. Since it is a large
>>project, we need more time to design and will send out the proposal later.
>>
>> Feel free to comment, thanks.
>>
>> 1: https://lists.apache.org/thread/39ct84dlxbo6zf0kktm15pyc7fd1n8cc
>> 2:
>> https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#
>> 3: https://github.com/apache/pulsar/issues/11766
>> 4:
>> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
>>
>>
>> 
>> Redesign Information Architecture
>> 
>> This page was last updated on 2021/11/4 by Anonymitaet.
>>  Landing page Changes
>> Content blocks On the landing page, categorize tons of info to several
>> blocks, which allows users to locate desired info quickly. Pulsar Good
>> example Docker doc we...
>> docs.google.com
>>
>> 
>> [website] website upgrade · Issue #11766 · apache/pulsar · GitHub
>> 
>> Preview make preview supported on netlify #11770 New syntax rules Click
>> here to see details. Action Base framework init website-next base project
>> #11770 Compatibility process implement custom link remark parser match
>> {@Inject: prefix:nam...
>> github.com
>>
>> 4:
>> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
>>
>> 
>> Redesign Information Architecture
>> 
>> This page was last updated on 2021/11/4 by Anonymitaet.
>>  Landing page Changes
>> Content blocks On the landing page, categorize tons of info to several
>> blocks, which allows users to locate desired info quickly. Pulsar Good
>> example Docker doc we...
>> docs.google.com
>>
>>
>> 
>> Upgrade Docusaurus
>> 
>> This page was last updated on 2021/11/4 by Anonymitaet.
>>  During upgrading
>> Docusaurus Issues to be fixed The follow issues need to be fixed: Function
>> https://pulsar.apache.org/docs/en/next/functions-package/ Invaild REST
>> API links Resolved i...
>> docs.google.com
>>
>>
>> --
>> *From:* Melissa Logan 
>> *Sent:* Friday, October 22, 2021 22:01
>> *To:* Dev 
>> *Subject:* Revote: Pulsar website concepts
>>
>> Hi all,
>>
>> I'm starting a new thread to vote on Pulsar website designs, per request
>> in
>> previous thread. This vote is being put forth through lazy consensus with
>> 72 hours to vote (1). Please reply here with your preferred site design --
>> option 1, 2, 3a or 3b.
>>
>> Background:
>> As discussed on this thread (2), my team offered to develop new website
>> d