blogs.perl.org

Well just another post-ette day here in the Moose-pen

Just another quick post-ette today as I want to quickly add in a feature to the results class that will help end uses with de-bugging.

Presently the results class look like thin when it is dumped

$VAR1 = bless( {
                 'is_error' => 0,
                 'DAD' => 'Database::Accessor::Driver::DBI',
                 'query' => 'UPDATE people SET people.first_name = ?, people.last_name = ? WHERE ( people.first_name = ? AND people.last_name = ? )',
                 'operation' => 'UPDATE'
               }, 'Database::Accessor::Result' );

useful info but it would also be nice to see what params are being used and if they are in the correct order; So a quick attribute add into the Database::Accessor::Result class;

I've just returned from a 2 week (and 2 Summit!) trip to Europe, specifically Berlin and Lyon. A couple months ago I was invited to attend the Perl Toolchain Summit 2017 in Lyon. Whenever I go to the EU I like to drop by Berlin to visit some friends.

One of my friends is Tina Müller, who works with me throughout the year on various open source things. We met 2 years ago at the Perl toolchain event in Berlin, that Tina helped organize. For the past 4 moths we've been concentrating on all of YAML as a lanuguage.

Specifically we've been making:

• The canonical YAML Test Suite for all YAML projects
• A multi-language YAML Editor for seeing how a given YAML text works in several language implementations at once
• The YAML Testing Matrix website for seeing how all the YAMLs work at a glance

I decided that we should have the first ever YAML Summit in Berlin along with our fabulous collaborator (and NimYAML author) from Stuttgart, Felix Krause.

This was my 5th year of being invited to participate in the Perl Tool Chain Summit (formerly Perl QA Hackathon). It was a real pleasure to be invited to a rebranded version of the same helpful event.

For the second year in a row, MetaCPAN was well represented at the event. This is important because it really does allow us to get much more work done. Getting everyone in the same room allows us to make decisions quickly and often deploy new ideas on the same day they've been discussed. Just like last year, we got a lot accomplished this year. I'm only going to touch on the work which I was directly involved with.

Read the full article.

I had the honour of being invited to the Perl Toolchain Summit 2017, held in Lyon. It was amazing to meet so many of my Perl heroes, and to work with them on Perl toolchain code for a concentrated few days.

The atmosphere, food, and company were all superb, and the opportunity to brainstorm, collaborate, and agree on things to work on in the future unmissable.

I was able to produce these bits of code:

• https://github.com/andk/pause/pull/136 - make PAUSE pass its tests as soon as you "git clone"
• https://github.com/ingydotnet/inline-c-pm/pull/63 - making Inline::C pass tests on Windows
• https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull/297 - fix a long-standing processPL bug that stopped Acme::CPAN::Testers::UNKNOWN working as designed
• https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull/278 - make EUMM work again on AIX
• https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull/299 - fix a regression on BSD-style make, and also make the first test of MYEXTLIB

Well test expand posette day here in the Moose-pen.

Not that have the first test in 20_where_basic.t working I figured I might as well expand on that tests and ensure the other SQL clauses are coming out in the format I like. So I added the following in;

This year I had one goal for CPAN Testers: Replace the current Metabase API with a new API that did not write to Amazon SimpleDB. The current high-availability database that raw incoming test reports are written is Amazon SimpleDB behind an API called Metabase. Metabase is a highly-flexible data storage API designed to work with massive, unstructured data sets and still allow for sane organization and storage of data. Unfortunately, Amazon SimpleDB is as it says on the tin: Simple. Worse, it's expensive: Like most Amazon services, it charges for usage, so there's a huge incentive for CPAN Testers to use it as little as possible (which made some of the code quite obtuse).

This was the second year I got invited to Perl Toolchain Summit 2017 (PTS) - I think I got even more done than last year.

Having so many people all working on similar projects really does lead to an exponential amount of productivity, both across projects and between Perl 5 and Perl 6.

I could write essays on what I was involved in, but a brief summary:

Thursday

• Launched new design for perl.org (babs did all the work)
• Discussed and setup env for grep.metacpan.org with toddr and atoomic
• Got Pete to start updating metacpan's vm
• Helped Haarg test and deploy a shim so `cpanminus` clients now use the v1 metacpan api (even though they hit the old v0 API), done using Fastly user agent detection and a new site just for this back compat that haarg has written.
• Discussion on metacpan v0 depreciation with haarg
• Start of discussion on improving search

Friday

I will be back in Oslo next week, and we still have a few spaces available in the
public class I'm teaching there next Tuesday. They'll be taking enrolments right up until 12 noon on Monday, so if you're in the area, there's still time to sign up and discover all the amazing new features and the many significant improvements that have been added to Perl in the past few years.

We'll also be organizing a public talk one evening, which I'll post about separately once the details are settled. Or you can keep an eye on Oslo.pm's Meetup page.

Se deg der, du vikinger av Perl!

Damian

Still in re-factor mode here at the Moose-pen.

Yesterday I had quite the success in taking a little more of the logic out of the DAD side side of things now the DAD writes not longer have to check to see if a predicate in a condition or filter has miss-matched parentheses or is missing at least the the default 'and' condition.

Before I move on I want to squish this little warning

Use of uninitialized value in join or string at...

which is really just sloppy programming on my part as this

I didn't get as much done on the final day of the Perl Toolchain Summit because I needed to get home for work on Monday. But I did manage to enlist others in helping me, which is even better.

Devel::Cover has always had a problem in that top level statements (those not in a sub) in modules cannot be covered. This is because perl throws away the optree as soon as it has executed. My knowledge of the internals has never been good enough to even work out a sensible plan for how to solve this, but fortunately Aaron Crane is a good deal cleverer than me and thinks he might be able to develop a solution. It may need perl to have extra hooks, or it might involve deep magic, or both, but at least the end of the tunnel is not pitch black any more. Thanks Aaron!

Introducing the new way to grep CPAN: https://grep.metacpan.org/

My co-worker Nicholas and I were honored to be invited to attend the Perl Toolchain Summit in Lyon, France last week. It was a great experience for both of us.

Earlier this year, I needed to answer some questions being put to me by the toolchain gang about the scope of the problem of build/test/install without . in @INC. However, grep.cpan.me was down that day. Additionally I needed to be able to execute Makefile.PL on each distro and see what happened. I tried to do some simple walking using CPAN::Mini when I was done, I played around with putting the data in git so I could use tools like git grep. On a whim I uploaded it to github but found 2 problems: 1. You're not allowed to have files over 50MB. 2. github won't search repos with over a certain number of files. I worked around the problem and uploaded the repo.

El próximo día 3 de junio celebraremos el primer Madrid Perl Workshop.

Ya podéis consultar la lista de charlas.

Participar en el evento es gratis y obsequiaremos a los asistentes con una camiseta, comida y café por cortesía de nuestros patrocinadores.
Os animamos a todos a venir.

Cerraremos inscripciones el viernes 19 a las 15:00.
Podríamos aceptar inscripciones de última hora, pero no garantizamos que queden camisetas para los últimos.

Podéis seguir las noticias sobre el evento en @PerlMadrid

ts re-factor day again here at the Moose-pen

With all my test passing since yesterday's post I think it is time I spend a little time re factoring before I move onto other things. Now as I said many times before I would like to have whatever is going to the DAD, Driver::DBI in this case, to be as free of logic errors as possible.

In this vain I noticed that when dealing with a where clause and predicates in general there are a two rules that should be enforced before any conditions or filters are passed into a DAD, First any parentheses that is opened must be closed and second two or more predicates must be joined by a condition.

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week.

Enjoy!

Everyone at TPF and the local DC-Baltimore Perlmonger groups are super-excited about the upcoming conference in June! We've posted almost all of the talk descriptions and are working on the full schedule.

Register now!

The core conference itself is Mon-Wed, and we're hosting some paid-tutorials on the days before and after. The outline:

Sunday 6/18 - Pre-Conference Tutorials

Perl in a Day (John Anderson)
Introduction to Moose (Dave Rolsky)
Perl Second Best Practices ( Randal Schwartz ) - 1/2 day
Unicode and Associated Punishments (Ricardo Signes) - 1/2 day

Monday 6/19 - Conference Day 1

Registation, Intro, Announcements, Snacks
Talks -- 4 tracks
Lightning Talks!
Keynote
Evening activities -- VIP and Sponsors Dinner

Tuesday 6/20 - Conference Day 2

Intro, Announcements, Snacks
Talks -- 4 tracks
Lightning Talks!
Keynote
Evening activities -- General Event

Wednesday 6/21 - Conference Day 3

Intro, Announcements, Snacks
Talks -- 4 tracks
Lightning Talks!
Keynote

Thursday 6/22 - Post-Conference Tutorials 1

Advanced Parsing Techniques (Mark Jason Dominus) - 1/2 day
Higher Order Perl (Mark Jason Dominus) - 1/2 day
MongoDB with Perl (David Golden)
New Perl (Damian Conway)

Friday 6/23 - Post-Conference Tutorials 2

Parsing with Perl 6 Regexes and Grammars (Damian Conway)

If you are in the area on August 25/26th, perhaps still in Europe after The Perl Conference in Amsterdam, and need another reason to come to the Swiss Perl Workshop, here it is...

Ladies and gentlemen, we are very pleased to announce that Damian Conway will be attending the fourth Swiss Perl Workshop as speaker, participant, and godfather!

Damian is well known for his talks, his modules, and of course his work on both Perl 5 and Perl 6.

You can sign up for the Swiss Perl Workshop here.

As always, thanks to our sponsors:
OETIKER+PARTNER | Perl Careers | GivenGain. If you would also like to sponsor the workshop then please do get in touch and see here for more information.

Well is bug squish day here in the Moost-Pen

Yesterday I manged to get my test to fail properly I guess today I better start looking at fixing the code that is breaking starting with my update;

I left print warn on and in my output I am getting this

DBD::DBM::db prepare failed: Couldn't parse at C:/Dwimperl/perl/site/lib/DBI/DBD/SqlEngine.pm line 340
 [for Statement "UPDATE user SET address = ?"] at 

and a little playing about with a small test script I discovered that I have to add in a 'where' clause to make an update work. I first have to change my test a little;

Location: Lyon, France
Date: 12 May 2017
Attending: SawyerX, Merijn (Tux) Brand, Todd (toddr) Rinaldo, Nicolas (atoomic) Rochelemagne, Lee Johnson, Aaron (arc) Crane, Leon (leont) Timmermans, Matthew (alh) Horsfall, Kenichi (charsbar) Ishigaki, Graham (haarg) Knop, Karen (ether) Etheridge, Stefan (nine) Seifert, Aristotle

We met to discuss the recent changes to @INC for Perl 5.26.

A timeline and summary of CVE-2016-1238 was given to attendees. P5P has not yet disclosed the original report that led to removal of . from @INC in 5.26 but will be doing so soon. It was requested that this be delayed due to the severity of the original bug.

As of 5.26.0, Perl will be compiled without . in @INC by default. There is a Configure option (-Udefault_inc_excludes_dot) to revert Perl to its 5.24 behavior but this is not recommended.

The ambush of WWW::Mechanize::Chrome shows more fallout before the module itself has been released. The module is one in a long line of browser automation modules I wrote, starting with WWW::Mechanize::Shell, reaching is breakthrough with WWW::Mechanize::Firefox and continuing from WWW::Mechanize::PhantomJS to WWW::Mechanize::Chrome.

PPI is a Perl document parser that enables easy analysis and manipulation of Perl source code in a structured manner.

It has been 2.75 years since the last PPI release, v1.218, so we're on a curve of shortening the gaps. ;)

Thanks to the efforts of many contributors to PPI, the support of the people at the Perl Toolchain Summit, the sponsors of the PTS, and specifically Matthew Horsfall (alh) (WOLFSAGE) i have been able to confidently release again after years spent grappling with overwhelming amounts of fixes to untested behavior, often with mutually conflicting results.

Particular thanks goes to the Sponsors for the Perl Toolchain Summit 2017:

Booking.com, ActiveState, cPanel, FastMail, MaxMind, Perl Careers, MongoDB, SureVoIP, Campus Explorer, Bytemark, CAPSiDE, Charlie Gonzalez, Elastic, OpusVL, Perl Services, Procura, XS4ALL, Oetiker+Partner.

Without the support of all of these people and companies this release would not have happened.

The highlights of this release are: