The second of the
bugs
that I am after squishing today was in Driver::DBI and in test case '15_alias.t'
It was dropping the elements/fields from the update command like this
Expected->UPDATE people SET first_name = ?
Generated -> UPDATE people SET
Looking at the code in Driver::DBI the line in question is the '_update' sub;
my (@field_sql) =
$self->_insert_update_container( Database::Accessor::Constants::UPDATE,
$container );
The first thing I checked was what was in the '$container' I was playing with. A line of two or waring and a run later it that turned out it was
Ever since Neil Bowers decided he would stop the "PullRequest Challenge" at the end of the year 2018 in this blog, I have been thinking over time what next after. He even wrote a blog about his ideas.
I am kind of addicted to this phenomena by now. I can't think of life without it. I then noticed someone called, Kıvanç Yazan, taking the initiative. He even setup a website PullRequest Club. Unfortunately I haven't seen much activities lately. Luckily he is giving talk at "The Perl Conference", Glasgow in Aug 2018, where I am also one of the speakers. I hope to meet him and discuss about the future of "PullRequest Challenge".
Felling a little better today as the mind is a little less foggy, that might change back on October
17
th though?
Today I am going to fix the first of the bugs I ran into
yesterday
;
Not a HASH reference at ,,,\t\lib/Database/Accessor/Driver/Test.pm line 13
# Looks like your test exited with 255 just after 6.
The first thing I did was look back at my API and see how I define a $container and it can be Hash-Ref or a Class or an Array-Ref of Hash-refs and Classes and I looked at my failing test. In this test I am using an array_ref;
The Perl Toolchain Summit (previously known as the Perl QA Hackathon) is an annual coding workshop for people involved in the Perl toolchain, testing, quality assurance, and related issues. 2018 marked ten years of the PTS, so it seems fitting that it returned to Oslo, where it was first held. I’ve attended a few of them, and I was very pleased to take part in this one as well.
Well, thanks to the very generous donations by my kin Perl Hackers, the fundraiser for the Raspberry Pi eBook that Timm set up and I eventually jumped on board for has reached its initial fundraising goal!!
I'm very excited, and even before we hit the target, Timm and I had been in communication preparing for, and even commencing some of the book's aspects.
I would like to personally thank everyone for their support, and want to give Gabor a shout-out for monitoring the progress of the fundraiser, and making it prevalent in the Perl Weekly for those couple of weeks there. We noticed a significant spike in activity following the release of the newsletter. Thank you everyone!
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
The Perl Toolchain Summit (PTS) is a yearly event that gathers the maintainers and contributors to the Perl Toolchain for four days in one room. Having all the people with both the knowledge and access to work on this critical corner of Perl all together in one place always leads to progress which is much more than the sum of those individual contributions. What is the Perl Toolchain? It is any part of Perl which is involved with modules, from creating, authoring, testing, uploading, distributing, loading, reporting on tests and test coverage, etc, etc. Projects like CPAN clients (cpanm, cpm), aggregation sites like MetaCPAN, CPANTesters, cpancover, and critical infrastructure like PAUSE and modules like Test::More/Test2 and many others are represented.
This year’s event was hosted in Oslo, by the indomitable Salve Nilsen, who first started this event in 2008 ten years ago, back when it was called Perl Quality Assurance Hackathon (QAH). Together with local organizers Stig Palmquist and other Oslo.pm members, as well as remote organizers Philippe Bruhat, Neil Bowers, and Laurent Boivin, (and others as well, I’m sure) it was again a wonderful event!
I just released RSLinux-v1.01, it's a new Linux distribution with its package
manager, build configurations, and a demo one liner init system all written
in Perl. It offers complete freedom on how you want it to be, like LFS, but
much much easier. And needless to say, if you're a Perl hacker you already
got extra advantage to use it.
The package manager is available on CPAN now, and there's also a VM image
on github so that you could easily try it out.
Please see the documentation for more information.
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;;
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).
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'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.
