Sorry I missed a few days it seem that when you have walking pneumonia it can turn into creeping pneumonia very easily. Who knew? I will have to start my year of daily posts again I guess I should be satisfied with 297 consecutive days.
Just a postette for for today and as usual it is just a quick all-up test post. For Database::Accessor it has been a while since I did a full pull on the repo and I got
GUIDeFATE, your favourite Quick-and-Dirty GUI designer for newbies is now acquiring a Web-socket interface. Now this is certainly not capable of competing with those genius applications Mojolicious, Catalyst, Dancer etc. Having only discovered Web-sockets a few weeks ago my yield is going to be decidedly sketchy. Of course a desktop interface is quite different to a web app...the machine running the interface is the same as the one the user is sitting at, and the program running the graphical output is the same as the one that is handling user interactions. When there is a client and server involved, a certain of communication is required between the two, both must of course be able to understand each other, even though they may be coded in different languages. GFweb (GUIDeFATE's Web-socket module) handles 1) the generation of the user interface 2) the initiation of a listening socket, 3) handles the communications between the two.
This year marks the 10 year anniversary of the Perl Toolchain Summit, formerly
known as the Perl QA Hackathon.
The Perl Toolchain Summit provides an opportunity for around 30 Perl
developers to get together for four days or so to talk about and develop the
infrastructure which surrounds Perl. This includes being able to build
modules, being able to test them on multiple systems, being able to find out
about them, being able to manage them, and many other related areas.
Salve Nilsen started the QA Hackathon back in 2008 in Oslo, and we returned in 2018
with Salve again being involved in the organisation.
This year I was very happy to discover that a number of people arrived in Oslo
with the idea of working on some area of Devel::Cover (the Perl code coverage
module) or cpancover (the service that provides coverage information for all
of CPAN).
You may remember a post a few days
ago
where I was starting the first of my practical Database::Driver::DBI tests against an Oracle DB I happen to have handy. I ran into problems right away as I was getting this generated SQL;
NSERT INTO people ( city, country_id, first_name,
last_name, postal_code, street, user_id )
VALUES( ?, ?, ?, ?, ?, ?, ? )
as the the container I was using was not being cleaned up so I was getting elements that where part of the 'address' view. My last few post cleaned up that problem and now when I run my test I get;;
I'm at the Perl Toolchain Summit 2018 in Oslo for a few days working with the MetaCPAN team. This is the 10th year of the summit (although confusingly the 11th actual summit!), and the 3rd year I've been able to attend.
I've setup our 2nd datacenter back to being a production ready cluster (of Elasticsearch). I added health checks and load balancing from Fastly (our CDN) to both the web front end (now using 4 nodes, 2 in each datacenter) and also setup our API (3 nodes in 1 datacenter as they all need to talk to the same elasticsearch). You can see what is running where in our domains document.
Dancer2 0.206000 has been released, and it is recommended that all users of Dancer2 should upgrade as soon as it is feasible to address several potential security issues:
There is a potential RCE with regards to Storable. We have added session ID validation to the session engine so that session backends based on Storable can reject malformed session IDs that may lead to exploitation of the RCE. Please see the Storable documentation for more information.
We have changed from HTTP::Body to HTTP::Entity::Parser (the same as Plack uses) for parsing requests. Apart from being faster, this change also resolves a situation when forwarding requests where the request body could be re-parsed without correctly seeking a filehandle to the beginning of the request body, potentially resulting in an infinite loop. The implementation using HTTP::Entity::Parser does not require the request body to be re-parsed. This addresses a potential DoS attack vector.
Its piddle with old code day here in the Moose-Pen
Yesterday I managed to clean up the '$container' param and now it only sends down to the DAD only items that match with the present view. After cleaning up all the related tests and adding a few more test in other test cases I have a little time last night to try some piratical use of Database::Accessor.
The first thing I discovered was it is very frustrating to the end user to send a '$container' down to a DAD have something unexpected happen and not know why or at least be able to see what was acted on.
Therefor I am going to expand my API yet again and include the both the passed in '$container' and the processed '$container' param in the 'Database::Accessor::Result' class.
Easy enough to implement but there are a few little problems. Being a param '$container' is only in local 'sub' level memory as it is entered by this calling structure;
I am just back from German Perl Workshop. The workshop is held every year and I finally had a chance to visit it!
I had these reasons to go:
Meet Perl hackers and community members who I have known online for years
Talk about TPF
Visit Perl, a small town in Germany
I'd like to express my gratitude for the organizers who worked hard to make it happen. They had to change the venue with a short notice and train track repair impacted the transportation but the organizers did a fantastic job.
The Perl 6 programming language had a turbulent birth. It was announced in
the summer of 2000 and the first stable language release shipped out only 2 years
ago, on Christmas, 2015. A lot has happened during that decade and a half,
yet the details are hard to piece together.
After my recent facelift to rakudo.org, I'm
working on a (second) facelift to perl6.org website.
Part of the work involves bringing all the Perl 6 deliverables under one umbrella, so the user isn't thrown around multiple websites, trying to find what to install. At the same time, we want to strengthen the distinction between Perl 6 the language and the compilers that implement it, as well as encourage more implementors to give it a go at implementing a Perl 6 programming language compiler.
Its take one step forward day here in the Moose Pen
today I am going to try and fix that stoppage I had
yesterday
. To recap I have a rule in my API that states that I can only 'update' or 'create' on elements that have the same view as the DA. So given this DA hash
I have published version 3 of my parsing timeline. It has many changes--
so many, it might be considered a new work. It is longer and now provides sources.
The new material includes coverage of combinator and monadic
parsing, and operator expression parsing,
making it considerably less Marpa-centric.
it's now available an improved version of App::DBBrowser with new features.
Some of the new features:
- attach databases to a SQLite database
- use sub-queries in different places of the statement
- choose if identifiers should be quoted or not
Yesterday I set up a new class that would generate a nice little set of DB table for me on what ever DB the end user may have by using a plug-in to supply the generation SQL. Today I greatly expanded that class but there is no real reason for me to dump it here as it is just more of the same from yesterdays post.
I did create a new class to test complete with a Data::Accesosr definition which is below;
Version numbers in Perl are very important; they allow orderly updating and maintenance of modules and distributions across the CPAN, and allow CPAN modules and consumers to require the versions of modules with the bugfixes or features they need. However, in this context, they are also a very unique beast with a complex and bumpy history that leads to some surprises for those who are not familiar with the nuances. These are the things CPAN authors should know about versions in Perl, and are nice for consumers to know as well.
Recently at $work we were discussing some of the behaviours of WWW::Mechanize when submitting forms. For instance, when you pass the fields parameter to the submit_form() method, Mechanize might take a very lax approach to submitting your data.
The Perl 6 IRC channel is an excellent place for all your Perl 6 needs. Any problem is solved in no time. However, it's not the best place for storing and searching those questions and answers. There's a place for that: StackOverflow.
