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
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.
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.
MooX::Press is a quick way of building a bunch of Moo roles and classes in one use statement.
The most basic example would be:
packageMyApp{useMooX::Pressclass=>['Foo','Bar'];}my$thing1=MyApp::Foo->new();my$thing2=MyApp->new_foo();# alternative constructor
But do-nothing classes with a constructor and nothing else aren't very exciting. Let's define a class with some subclasses which have attributes and roles and methods and stuff.
Spoiler Alert: This weekly challenge deadline is due in a few days from now (October 27, 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.
Challenge # 1: Illegal Division by Zero
Create a function to check divide by zero error without checking if the denominator is zero.
Illegal Division by Zero in Perl 5
Perl 5 has a number of modules to implement exception handling using the try ... catch pattern found in a number of other languages, such as, for example, Try::Tiny or TryCatch. Even Autodie might actually fit the bill. But, because this is a coding challenge, we prefer to avoid using modules that do the work you're supposed to do.
In fact, not doing anything special will check the division by zero, as shown in these one-liners:
Well the first thing for my S3 todo fixes was to get everything back up to github for my fix for 'GetBucketLocation' once that was done I decided to tackle the rest of the 'todo' tests.
I started out with 'GetBucketPolicy' but I notices that when I set up a real test for the code I get this as the content response;
Very odd I am getting JSON back from 'AWS' not 'XML' maybe something has changed ? I think this time on the AWS side of things or maybe my botocode is out of date? I will have to do a little digging.
On the aws site I found this
Response Syntax
HTTP/1.1 200
{ Policy in JSON format }
in the latest version of the S# API for the 'GetBucketPolicy'.
I went to the London Perl Workshop 2019 this weekend. I've been attending the London Perl Workshop several times in the past, and it has always been a great workshop. This year the workshop had a brand new team of organisers, and they did a great job of following up on the legacy that is the London Perl Workshop (LPW).
Going to London
My LPW weekend, didn't start that great. I had a flight from Copenhagen to Gatwick at nine in the evening, but the flight was delayed by almost an hour. This could mean missing the last Gatwick Express train, which would mean I would arrive at the hotel past midnight. Not the best start of a short weekend trip to London.
Finally the pilot was allowed to take off, and he managed to catch up somewhat for the lost time. I had a seat on the second row, I had booked that to be able to get quickly off the plane and get to my train.
The London Perl Workshop was on Saturday, and it was awesome! If you missed it, or you'd like to reminisce, our Twitter feed has pictures through out the day. Hopefully there will be some write ups posted soon.
As well as getting the talk videos live and actioning your feedback (please fill in your survey, it really helps!) we want to say a massive thank you to everyone who made the day such a success. The attendees, the speakers, the venue and our sponsors - without any one of you it wouldn't have been the same, and in particular we'd like to thank our Platinum Sponsor Booking.com for their support.
Booking.com is a large Perl shop with some of the greatest developers and as a company they sponsor almost all Perl events around the globe to support the Perl community.
I finally (well a few days ago) had a response to another of my questions up on gitihub;
-->me
I added in th status as you suggests. I found it under botocore as "location":"statusCode", It is used in a number of other classes
-->they
This means that we can make the builders put the trait on the appropiate attributes, which I see you already found ?
-->me
I added it in as a new trait as you suggested, not 100% sure on the name though
-->they
I think the name would better be ParamInStatus (just as a reflex of the other traits).
-->me
please have a look and see if I am on the right track.
-->they
I think you're on the right track ?
So I have switched over to my 's3ObjectTagging' branch and I think I all have to do is change the name of my trait from 'ParamInResponse' to 'ParamInStatus' which I found in three files and did a simple change and then reran the test and got;
Write a script to list dates for Sunday Christmas between 2019 and 2100. For example, 25 Dec 2022 is Sunday.
I used the core module Time::Piece to check the dates.
It’s easy to create a string representing Christmas: just concatenate the year with '-12-25'. The module’s strptime method can be used to create an object if we provide a format of the input string, in this case it’s '%Y-%m-%d'. The object’s method day_of_week now tells us what day the object represents, 0 corresponds to Sunday, which is the day we’re interested in.
It’s that time of the year again! The 36th Chaos Communication Congress (36c3) is coming to Leipzig in Germany. From December 27 to December 30 my hometown will hold the yearly convention of the Chaos Communication Club. It’s the largest hacker conference in Europe and also covers topics like politics, science, making and art.
Vouchers for receiving a ticket through any CCC-related community are being distributed right now. Reach out immediately to your nearest CCC Erfa, hackerspace or similar community to get a ticket smoothly! For the more adventurous there will be public presales on November 8, November 10, November 21. Although the queuing system is sophisticated these are usually sold out in seconds.
The London Perl Workshop is today! If you can make it, hopefully you have already planned your journey there - please remember we're at a new venue this year. If you're thinking about your journey home, after the event we are going for after drinks, with food provided by our sponsors at the Running Horse in Aldgate. We'd like to thank our last gold sponsor Eligo for their continued support of London Perl events.
Eligo are a niche boutique recruitment consultancy with a team of dedicated Perl Consultants. We live and breathe our markets. In fact we like to think we are as passionate about the sector as those who work within it. If you want proof of it stop by and meet Rick Deller one of our Senior Perl Consultants at LPW today.
Well I though I hit the correct fix when Paws does its XML parsing and drops the 'Root' node but I found I have to apply some sort 'trait' to my class rather than an attribute so I am going to start this time with my code for 'RestXMLResponse.pm' first and then work that fix back into boto and the templates.
The Camelia mascot of the language now known as Raku is a brightly coloured metaphor for the transition from Perl 6 to it's new identity. My hope is that having emerged from it's cocoon, Raku will flap it's wings and fly skyward, boldy seeking new adventures.
I congratulate the team for making this decision, specifically Elizabeth Mattijsen for being so bold as to propose the change request that triggered the end game. No doubt other people where involved that I am not familiar with, they deserve generous praise and recognition too.
My personal involvement in Raku/Perl6 is literally zero. So I make this post as a person for whom Perl 5 continues to be a delight for personal projects, and sadly declining professionally.
Reading through the public comments there are a lot of strong feelings - some of them hurt feelings. Humans are fundamentally emotional creatures, and the grief associated with strong disappointment follows the same path to acceptance no matter how rational a person fancies themselves.
Happy Friday! If you are coming to the London Perl Workshop tomorrow, or even if you can't make it tomorrow but are in London today, you are welcome to join the pre workshop social this evening from 18:30 at The Draft House, Seething Lane.
The first few rounds will be courtesy of our fantastic sponsors, so today we'd like to thank Pirum for coming on board this year as a gold sponsor!
Pirum is a small dynamic FinTech company established in 2000, which provides Software-as-a-service the top-tier financial institutions in Securities Lending throughout the world.