blogs.perl.org

Sponsors make it possible for us to run LPW without charging for tickets, and as an organiser last year Pete Sergeant knows just how important this is! Thank you Perl Careers for your ongoing support.

Here is the coverage of Faster.xs in the module Gzip::Faster:

http://cpancover.com/latest/Gzip-Faster-0.21/Faster-xs--branch.html

It suggests that most of these statements aren't tested. But actually they are, more or less.

What seems to be happening is that SvTRUE is a macro with about five or six different tests:

https://github.com/Perl/perl5/blob/blead/sv.h#L1761

and so to get "coverage" of all the SvTRUEs here I'd need to send a string, an integer, a floating-point number, and so on and so on. But would that actually tell anything about Gzip::Faster? In fact it wouldn't. It would just be testing whether SvTRUE from Perl's core was working correctly or not.

The latest version of Dancer2 is out the door, and it is chock full of changes! A few new features worth noting include:

• send_as() now allows you to easily send plain text content (in addition to JSON and other formats (Steve Dondley)
• Mutable serialization with custom mappings (Russell @veryrusty Jenkins, Yanick Champoux, Daniel Böhmer, Steven Humphrey)
• A new no_default_middlewares setting to allow Dancer2 applications to work with ETag (and similar) middlewares in the Plack stack (veryrusty)

There have been a lot of documentation improvements made, driven largely by the members of our awesome community.

The full changelog is as follows:

Is may be the end of the errors Day here in the Moose-Pen.

I spen quite a bit of time mulling over the various options and possible solutions to the rater large mess I made yesterday with my recursive call to a eval.

I did manage to do a very long coded version where de-factored my code back to what it was when I starter earlier this week. A block of code for each 'undef' sistuation.

I wasn’t really satisfied with that as it was ugly, unmaintainable and I think very fragile once I got into more that two levels of recursion on my evals.

What to do?

Well I had a peek at the guts of 'AllErrors' MooseX and from the I could see that it was warping anything I was doing a new with its own 'around BUILDARGS' so that explain why I was getting three errors rather than just one. I also means that I have to do another shameful act;

I've like to propose adding a ROADMAP section to module documentation.

It would be a *short* summary of planned changes for future versions, noting what features would be removed or changed, or upcoming new features that will be added.

More detailed roadmaps should be put in a separate file (e.g. `ROADMAP` or `ROADMAP.md`) that should be referred to in the section. Or link to the roadmap if it's online.

I've been reviewing the coverage of the tests of modules using metacpan.org.

It is pretty handy for finding stuff which is not tested.

I tried it on this module:

https://metacpan.org/release/Directory-Diff

I noticed that a lot of the code had no tests, and there were also some completely unused subroutines.

I removed some of the unused subroutines and wrote some tests for the remaining things, and was able to improve the coverage:

This seems quite handy.

We're in Chicago and we're hacking on MetaCPAN.

Read the full post.

Still stuck in error land in the Moose-Pen.

As I finally got the 'add_condition' to work I still needed to add in a few more tests for the other three 'dynamic' attributes, gather, link and sort.

Well I started with the easiest first 'sort' and on the 'undef' I am getting the now very familiar;

Attribute (name) is required at D:\GitHub\database-accessor\lib/Database/Accessor/Types.pm line 348

It did not take me very long to back track this one to the '_element_coerce' sub in my 'Types' class; As this had the same sort of fall though 'if' case like '_predicate_array_or_object' I at first added my check for undef code in the final 'if' of that statement;

On behalf of the development team, it brings me great pleasure to announce the 6.d ‘Diwali’ major version release of the Official Specification of the Raku Perl 6 programming language.

Please see the PDF of our Release Brochure for all the details: marketing.perl6.org/id/1541379592/pdf_digital (print-friendly version is also available on marketing.perl6.org)

If you are unable to view PDF documents, most important details are also available as a plain text file in the repository github.com/perl6/roast/blob/master/docs/announce/6.d.md

Compiler releases with 6.d as their default language version will follow their standard release scheduling (for Rakudo compiler, release process will start on 2018-11-17)

Happy Diwali!

Do you want to post an article in this year’s #mojolicious #AdventCalendar? I’ve just posted a call for articles in the mailing list. You do and know things that other people want to learn about, I promise!

Read more in Call for posts: Advent Calendar 2018!

(Please reply there, as I don’t get notifications from this site on comment.)

While writing plugins we can do something:

$app->plugin( Auth => {
    user_check =>  sub{
        my( $user ) =  @_;

        # authentication_code_here;
    },
);

But I prefer to keep my sturtup sub clean. Thus I route to controller’s action:

$app->plugin( Auth => { auth_check => 'auth#check' } );

Doing so I need to check in my plugin passed value. Is it sub or shortcut auth#check?

And to simplify checking I implement next route shourtcut

It is another shame day here in the Moose-pen

I never like taking out code but that is the first thing I had to do today. So all the code changes from yesterday have been rolled back and I still have the same problem;

Attribute (predicates) does not pass the type constraint because: Validation failed for 'Predicate' with value undef (not isa Database::Accessor::Predicate) at D:\GitHub\database-accessor\lib/Database/Accessor/Types.pm line 349# 

Namely an error message that tells me nothing of where my mistake;

$da->add_condition(  undef);

happened.

I take a good number of 'warn' statements throughout my 'Types' class finally find a spot where I can intercept and create a better error message.

I eventually tracked it down to the '_predicate_array_or_object' sub in the 'Types' class;

DBD::SQLite 1.59_03 (with SQLite 3.25.2) is a release candidate of the next stable DBD::SQLite. Notable new features by the upstream are PostgreSQL-style UPSERT (3.24.0), ALTER TABLE table RENAME COLUMN oldname TO newname (3.25.0), and window functions (3.25.0), among others.

It also contains a fix that changes how to store values in a PerlData virtual table. If you use PerlData virtual table, this may affect your applications.

I'll wait for about a month as always, and release 1.60 at the end of November if there's no blocker nor request to wait more. Thank you for patience.

Thanks to the hard work of Shadowcat Systems, the individual videos are now available:

Wednesday

cPanel Theatre

• ‎Discourse Without Drama‎ - Ruth Holloway (‎GeekRuthie‎)
• ‎When diff is not enough - H.Merijn Brand (‎Tux‎)
• ‎Types in JSON‎ Choroba
• ‎Language design in a Perl without Larry‎ - Leon Timmermans (‎leont‎)
• ‎How Geizhals took out ImageMagick before ImageMagick took *us* out.‎ - Nicholas Clark
• ‎Rescuing a Legacy Codebase‎ - Curtis Poe (‎Ovid‎)
• ‎Perl, Caching, and Memory Leaks‎ - Lee Johnson
• ‎Lightning Talks Day 1‎

Zoopla Theatre

• The JobCenter, an Orchestration Workflow Engine‎ - Wieger Opmeer (‎a6502‎)
• A bag of mojo sweets‎ - Diego Kuperman (‎diegok‎)
• ‎How to join CPAN Pull Request Challange‎ - Kivanc Yazan
• ‎TPF Update‎ -Makoto Nozaki (‎makoto‎)
• 10 things I've learned working with Perl 6 documentation‎ - Juan Julián Merelo-Guervós (‎jmerelo‎)
• ‎Building a concurrent version control system mirroring CVS and Git‎ - Ben Edwards

Pirum Theatre

Still cleaning in here in the Moose-Pen

Well was all ready to move onto the final documentation and distzila stage of Database::Accessor and then I ran into a few little tings when I reran the full test suite.

First there was this annoying warning;

Use of uninitialized value $error_package in string eq at \GitHub\database-accessor\lib/Database/Accessor/Roles/AllErrors.pm line 59.

a simple fix really just this;

        my $on ="";
--      if ($error_package eq "Database::Accessor::Element"){
++      if (($error_package)  and ($error_package eq "Database::Accessor::Element")){
           $on = " Possible missing/invalid key in or near:\n"
                 . Dumper($Database::Accessor::Types::LAST);
        }

Read this article on Rakudo.Party

Every year since 2009, the Perl 6 community publishes a Perl 6 advent calendar, in the form of blog posts on perl6advent.wordpress.com.

To keep up this great tradition, we need 24 blog posts, and volunteers who write them. If you want to contribute a blog post about anything related to Perl 6, please add your name (and potentially also a topic already) to the schedule, and if you don't yet have a login on the advent blog, please tell Zoffix or someone on #perl6 IRC chat your email address so that they can send you an invitation to Wordpress for the site.

Perl 6 advent blog posts should be finished the day before they are due, and published on midnight (UTC) of the due date as publishing date.

If you have any questions, or want to discuss blog post ideas, please join on the #perl6 IRC channel on irc.freenode.org.

The SSL certificate of the domain of the Perl 5 repository has expired from 10/19.

https://perl5.git.perl.org/perl.git

I would like to share a minor fixup when using Perl with Perlbrew on MacOS.

After updating to MacOS X Mojave... I was not able to compile any XS module.. or even reinstall a different version of Perl itself...

Here one example output when trying to compile Clone for example

Still in mop up mode here in the Moose-Pen

I finally found a way (well not a good one) to generate an even better error message to my end users. You are of course quite familiar with this type of message;

Database::Accessor add_condition Error:
The following Attribute is required: (Element->name)

With constructor hash: { 'operator' => '=', 'left' => { 'view' => 'People', 'name' => 'last_name' }, 'right' => { 'left' => { 'name' => 'salary' }, 'right' => { 'expressionx' => '*' }, 'function' => 'LEFT' }, 'close_parentheses' => 0, 'condition' => 'AND', 'open_parentheses' => 1 } Very hard to find out that it is the 'expressionx' that is giving us grief. With the changes I have just completed I now get