blogs.perl.org

From the blurb:

Convos is the simplest way to use IRC. It is always online, and accessible to your web browser, both on desktop and mobile. Run it on your home server, or cloud service easily. It can be deployed to Docker-based cloud services, or you can just run it as a normal Mojolicious application.

Check it out at: https://convos.by/ or on Github.

The UI style is familiar to users of popular "Team Communication" platforms.

There is an online demo running at demo.convos.by. Register with your email address and try it out. There should be someone lurking in the #test channel.

Well after the panic stations I talked about in my last post. I have calmed down a little. It seems that huge check in was for the compiled version of the code base and 99% of the changes where just auto-auto-generated stuff chugged out by boto when it re-compiles.

That being said I did find this thread while investigating the mother of all pushes; https://github.com/pplu/aws-sdk-perl/issues/244

Requirements for stabilisation?

shadowcat-mst commented on 24 May 2018
So, a number of components in Paws have something like this -
https://metacpan.org/source/JLMARTIN/Paws-0.36/lib/Paws/S3.pm#L2
Is there a list anywhere of what's required to get to the point where that warning can go away? If not, how would we go about getting to a point where there was such a list?

There are 135 thousand releases on CPAN now. In those releases there are about 3.8 million files with extensions .pm, .pl, .t or .pod.

Here is a link with a small research what symbols are used for indentation in all that files.

There is obvious trend, but unfortunately in this article there is no exact answer why it happen.

https://squareperl.com/en/tabs-vs-spaces-in-millions-of-perl-files

I start to write SPVM Language Specification in English.

SPVM 1.0 Language Specification

I write SPVM language for 3 years. Language Specification is completed by 95%.

It is time to write SPVM Language Specification in English.

Let's try to

cpanm SPVM

I missed this release but it's only a little over a month old, so its still news.

Sympa 6.2.48 is the newest stable version of Sympa 6.2.

Sympa is an electronic mailing list manager. It is used to automate list management functions such as subscription, moderation and management of archives. Sympa also manages sending of messages to the lists, and makes it possible to reduce the load on the system. Provided that you have enough memory on your system, Sympa is especially well adapted for big lists. For a list with 20 000 subscribers, it takes 5 minutes to send a message to 90% of subscribers, of course considering that the network is available. Check out the full list of features.

From the release notices

• Data sources: Codebase has entirely been rewritten. It will work a bit faster with less memory usage in exchange for some changes on behaviors.
• Perl: From now on, Perl earlier than 5.10.1 will never be supported.

The full Change Log is here.

RPM Packages are in Fedora and EPEL, and Sympa is in the FreeBSD ports tree. Otherwise you can just install from source tar ball.

Also, a new Logo for the project has been proposed. Check it out too.

So I have been happily plugging away at the Paws 'S3' actions and my little Boto fix of

/{Bucket}?action
/{Bucket}?action&id={Id}

I was able to get all of these 'Actions' to work;

• DeleteBucketAnalyticsConfiguration
• DeleteBucketInventoryConfiguration
• DeleteBucketMetricsConfiguration
• GetBucketAnalyticsConfiguration
• GetBucketInventoryConfiguration
• GetBucketMetricsConfiguration
• ListBucketInventoryConfiguration
• ListBucketMetricsConfiguration
• PutBucketInventoryConfiguration
• PutBucketMetricsConfiguration

Also my 'Flatten' fix seem to clean up at least five or six others so a good day. Then I ran into this one; 'GetBucketPolicy' and on reading the ASW API doc I saw;

Frequency Table

Create a script that either reads standard input or one or more files specified on the command-line. Count the number of times and then print a summary, sorted by the count of each entry.

The original title of the task was “Count instances”, but I’ve always known the output as the “frequency table”. For years, I’ve used the following bash script to produce it:

#! /bin/bash
cat "$@" | sort | uniq -c | sort -n

The first element in the pipeline is cat. It outputs all the files given to it as arguments, or the standard input if there are no arguments. sort sorts the output so duplicate lines are adjacent, which is needed for uniq. Its -c argument means “count”: it prepends the number of occurrences to each line. The final sort is invoked with -n for “numerical”, i.e. it sorts the output by the number of occurrences.

Creating a similar table in Perl is a FAQ. We store each line in a hash, incrementing the corresponding value while reading the input line by line.

If we look carefully at the assignment of the task, though, we can notice that the output should be formatted differently: the numbers should go last and the columns should be aligned. Also, there’s the extra credit which we definitely want.

When I started working at SUSE, one of the first things I worked on is the maintenance of the perl modules repository in the openSUSE Build Service (OBS).

We are using a tool called cpanspec to create .spec files from CPAN modules. From the spec file, the OBS then builds rpm packages.

I noticed there are a lot of modules missing information, or having other problems that prevent us from automatically create a working .spec file.

October has been always the busiest month of the year for one annual event Hacktoberfest. However this time, we have had London Perl Workshop annual event as well. On top of all these, I have had to manage Perl Weekly Challenge. I have been participating Hacktoberfest since 2015. It was first introduced to me by Neil Bowers. Last year, I contributed 155 Pull Requests in the month of October. Having done this, I never thought I would ever break this record. Luckily I submitted 160 Pull Request last month.

Here is the breakdown:

• Merged: 90
• Close (unmerged): 17
• Open: 53

The next action I had a crack at was 'PutCORSConfiguration' and I was getting the usual;

<Error>
  <Code>MalformedXML</Code>
  <Message>The XML you provided was
 not well-formed or did not validate against
 our published schema
  </Message>
</Error>

At this points in my Paws adventure I checked the API doc for URI Request Parameters of the PutCORSConfiguration;

PUT /?cors HTTP/1.1 Host: Bucket.s3.amazonaws.com Content-MD5: ContentMD5

and I see I don't have to deal with the 'id' in the 'URI' bug here as I get what I want in the request URI;

We are lost.

Temptation and desires will make us lost.

Where is Perl going after Raku begins to take a different path?

Raku provides new values.

Perl provides traditional and conservative values.

If you lead Perl to Raku, Perl will fail.

If you ask Raku for Perl, Raku will fail.

When we talk, we need to be aware of the difference between Raku and Perl.

We are lost.

Those who like traditional Perl have respected SUPER and bless.

Those who aim for Raku have thought that SUPER and bless are failures.

That has become a negative campaign against Perl.

We may need to go back to the fundamentals of what Perl offers.

The Perl language is a good language, but the Perl community continues to fail in marketing.

What benefits does Perl offer?

What is Perl's mission?

Who is a Perl user?

Where is Perl used?

What are the strengths of Perl?

What is Perl's vision?

We talk a lot about the details of the language, but haven't talked about the value that Perl offers to society.

Isn't it time for the Perl core team to start talking about Perl marketing?

I've spent more than four years working on Raspberry Pi stuff for Perl, and although it's only garnered a relatively small but thorough interest, it's been a wonderful one to be a part of.

Mozilla has opened up a new IoT Platform, and I'm wondering if it'd be worth the time to provide a Perl interface to it or not.

Thoughts?

These are some answers to the Week 32 of the Perl Weekly Challenge organized by Mohammad S. Anwar.

Spoiler Alert: This weekly challenge deadline is due in a few days (November 3, 2019). This blog post offers some solutions to this challenge, please don’t read on if you intend to complete the challenge on your own.

This week, both tasks were contributed by Neil Bowers.

Task # 1: Word Histogram

Create a script that either reads standard input or one or more files specified on the command-line. Count the number of times and then print a summary, sorted by the count of each entry.

So with the following input in file example.txt:

We last left out PAWS hero she was just about ready to fix the S3 'PutBucketAnalyticsConfiguration' call. Having first fixed up the botocore json file to properly define the URI for the call.

She now had to find a way to get the 'xmlns' schema attribute add to the root of the XML that is sent to the API.

Turns out I was in very virgin territory there has been no Paws code to take this into account and checking the py code it was not very helpful so I have to put my thinking cap on for this one.

I was thinking I could just make it a new 'trait' like I did for the 'Status' attribute but then I remembered some of my XML from years ago the the 'xmlns' always should be in the root node so It will appear only in one place so not really an attribute trait.

This is a sensible step forward for both languages.

The moderators of r/perl have had a discussion and we've agreed that going forward, this subreddit will be for the discussion of Perl 5 (and, I guess, earlier versions). Posts about Raku are off-topic here. I think that's what most readers here wanted and I think the Raku people will welcome the separation too.

See all the discussion at https://www.reddit.com/r/perl/comments/dmtxk1/raku_posts_in_rperl/

At first, see the following entry.

Data Science and Perl

Our company goes into many other companies and helps them build new Perl systems or fix old ones. Needless to say, we see how many companies work and a typical example is one of our clients I'll call "AlphaCorp." They use lots and lots of Perl. Their primary web site is almost entirely Perl. So when I went in to help them with their A/B testing (amongst other things), I was surprised that they also used a lot of Python. It turns out they had a specific need that Python fills and Perl does not: data science.

After thinking a few weeks, I create the plan to do Data Marketing.

Data Marketing Plan by Perl modules

This is Japanese. Please translate it using google translation.

The official Perl documentation site at https://perldoc.perl.org was recently overhauled. Independently, I put together a reimagined documentation site that would be hosted at https://perldoc.pl. In the interest of providing a documentation site that best serves the needs of the Perl community, we need your feedback. Please give both sites a try, in-depth if you want, or just how you would most commonly use the site. What do you like about the design or the functionality of each site? What is missing or can be improved? Any feedback regarding what you want from the Perl documentation site is helpful and appreciated. Please leave comments here or in the linked posts by Monday Nov 18th.

Reddit comments

PerlMonks comments

Well the saw-buck edition of Paws proved to be a real tough one a least for me. I my last post I was just thinking of fixing all the S3 calls that do not have a test I was just going to start with all the delete calls but I decided to rater take a functional approach and tackle the calls in that order so I started out with the 'Analytics' calls

• DeleteBucketAnalyticsConfiguration
• GetBucketAnalyticsConfiguration
• ListBucketAnalyticsConfigurations
• PutBucketAnalyticsConfiguration

The first one I was going to play with was the 'PutBucketAnalyticsConfiguration'. This is where I ran into a little bit of a sticky wicket.

I noticed that I could easily write up a 10_resposne test but no where did I see in the test case that would test how the data is being called?? There are a few S3 call tests in 05_service_calls.t which look like this

Division by zero

Create a function to check divide by zero error without checking if the denominator is zero.

Perl already checks the denominator when dividing. All we need to do is to catch the exception it throws and check it instead of checking the value of the denominator.

The following division subroutine uses Try::Tiny to catch the exception. It’s a good practice not to use the low level eval, see for example Bug in eval in pre-5.14 for the reasons.

DISCLAIMER: All photos courtesy to the official twitter handle of London Perl Workshop.

As you know, LPW2019 just happened last Saturday 19th Oct 2019. It was my second year as a member of LPW Organizing team. Although I was the least active members in the team as compared to others. On the day, I arrived the venue around 8:10 am and saw Katherine, Tom and Lee unloading event materials from the cab. I joined the team and gave helping hands. I was managing the registration desk along with Katherine. People sarted arriving about 8:30 am. It was always great to see so many friends.