The porting of GraphQL to Perl 5 (sponsored by Perl Careers) continues. With v0.12, released 10 Oct, it is possible to run queries and return results. This includes the introspection query built in to GraphQL.
Now there is a Dancer 2 plugin: Dancer2::Plugin::GraphQL. This allows you to make a Dancer2 app that serves GraphQL, and - if configured suitably - serve the superb GraphiQL interface to interactively explore and query your schema, with type-ahead.
It's that time of year again. The core MetaCPAN hackers are going to be hacking on MetaCPAN next month. We are still looking for some sponsors. Read the full post.
Login to Shippable using your GitHub or Bitbucket credentials.
Enable the project
On the Shippable landing page, select your subscription from the Subscriptions dropdown. This should be the subscription where you forked the repository. Click on your GitHub/bitbucket name
click on the Enable Project button. If you have not enabled any projects on Shippable, you will be directly be taken a page which shows a list of your repositories.
Find the Docker-CI-perl project and click on the Enable button. You will be taken to a page which shows that Status as Not built, towards the right of that table there is a build button. Click on that to start a build.
while the build is running you can on the id ( # column ) to look at the console. Once the build is done you can look at the test results.
Today I managed to get the time to create '25_exe_array.t' which tests DBI execute array and it went quite well. No real story on that one just with my new 'Test::Utils::sql_param_ok' function I was able to quickly expand it out from just 3 tests to 6 in a few minutes.
I then moved on to '30_where_basic.t' where the idea was to test the basic parts of a 'condition', The basic parts being simple single level predicates mixing elements, functions and expressions.
After creating some 64 tests and giving it a few goes to get rid of the usual typos I ended up with 24 fails out of the 64 and all of them where much like this example;
We are a week into the Dancer 2017 Survey, and we have received 77 responses to date. The Core Team has received a lot of great feedback from the community so far, and it has already resulted in some exciting new work, the most notable of which being the release of Dancer2::Plugin::Websocket by Yanick.
The Dancer Core would like to thank those of you who have taken the time to respond thus far, and would like to encourage those of you who have yet to respond to take a few minutes and give us your feedback. You can help determine the future of Dancer!
If you are interested in helping with Dancer, but are unsure of where to begin, check out the list of issues on Github. There are a number of issues that are not only tagged as being up-for-grabs, but many are even beginner suitable. If you have any questions, please engage with us on IRC, Github, or our mailing list.
On behalf of the Core Team, thank you, fellow Dancers!
Jason
Been half-following Perl 6 development and wondering whether it's for you? This year's London Perl Workshop (Nov 25th) features:
Simon Proctor gives us "Perl 6: A Whistle Stop Tour", aiming to answer the fundamental questions: is this useful? Could I use this in production? Should I use this in production? Why might I want to?
Granada's JMERELO looks into "Perl 6 as a first language". With its use of Unicode, generosity of operators and their combinations, and the amount of baked-in data structures, Juan argues Perl 6 makes an excellent choice for teaching programming and computational thinking, as well as more experienced developers who want to stretch themselves.
Don't want to just sit on the sidelines? Lance Wicks runs an interactive workshop on Bailador, the Perl 6 web framework, covering everything from rakudobrew up to the deployment and hosting of your first Bailador project. The workshop is designed to be beginner friendly: it doesn't matter if you're new to web development, Perl6 or Bailador, there's something for you.
Attendance at the London Perl Workshop is free of charge thanks to the generosity of our sponsors - you can signup and find out more about the conference here: http://londonperlworkshop.org
Code golf, for those unaware, is a game designed to let you show off your code-fu by solving problems in the least number of keystrokes. It goes without saying that Perl lends itself well to golfing.
code-golf.io is a new website that lets you write such solutions, have them scored in real-time, and compete with other users on per-hole, per-language, and overall leaderboards.
The project is very young and will grow to have more holes, more languages, and more features over time, but it's also open source, so feel free to help it along. Patches welcome!
So come one, come all, and either add to Perl 6's dominance, or knock Perl 6 off the top spot with your awesome Perl 5 one liners! JavaScript, PHP, Python, and Ruby are also supported for the heathens :-P
And I sing, the littlest birds sing the prettiest songs
…
For us Perl types it should be
And I swear, the littlest typos make the ugliest bugs
...
You will remember that I left off
yesterday
with this little bug;
Expected SQL--> SELECT people.first_name, people.last_name, people.bonus * abs(?) FROM people
# Generated SQL-> SELECT people.first_name, people.last_name, people.bonus * abs(?),1 FROM people
I was getting ',1' tacked onto the end of some of my generated SQL.
This one proved rather frustrating to track down, and it took much more time than one would expect. I suspected it has something to do with the 'function' part of the '_field_sql' code so I started there but despite my best efforts of adding warnings on each line I could not find it.
Hello all,
Quick update on the status of AI::MXNet.
Recently MXNet proper got a cool addition,
new imperative PyTorch like interface called Gluon. If interested please read about it at
Gluon home page
.
I am pleased to announce that Perl (as of AI::MXNet 1.1) is joining a happy family of Lua and Python that are able to express ML ideas with Torch like elegance and fluidity.
Today's code is from Perl examples, and if you would like to understand it deeper please read the details at
Gluon DCGAN example
.
For twenty years Iridium Communications Inc has provided global communications with a fleet of 66 satellites, plus spares. For most of that time the satellites have had the same design, and a consequence of that design was their ability to produce very bright and predictable flares due to the reflection of the Sun off their Main Mission Antennae. Beginning January 14 2017, though, satellites of the original design are being replaced by a new design that does not flare nearly as often or as brightly.
Perl module Astro::Coord::ECI::TLE::Iridium, part of the Astro-satpass distribution, predicts these flares. It seems to me to be time to start thinking about how to retire this module.
If you've been following Rakudo's development since first language release on
Christmas, 2015, you might've heard of numerous people working to bring CPAN
support to Rakudo Perl 6.
Good news! It's finally here in usable form and you should start using it!
Let's talk about all the moving parts and how to upload your dists
to CPAN.
The Moving Parts and Status Report
All of the heavy lifting has been done awhile back, during Perl Toolchain Summit and other times. I wasn't present for it to know the details, but to
catch up you could
join #perl6-toolchain chat and talk to humans or read the channel log. PAUSE/CPAN
support for Perl 6 dists was implemented and zef module installer was trained to check for CPAN dists
as well as our GitHub/GitLab-based ecosystem (called "p6c").
Its test test and test again day here in the Moose-pen
Today I added in over 70+ tests into '20_fields.t' and I went though almost every conflagration of fields, params, expression and functions I could think of even the expression from hell from this post.
I did today's work by the book meaning I did all the tests first then I did the debugging. Now I am not going to dump 450 plus lines of hash key value pairs here as that would really piss a few people off and I might loose a reader of two, as if anyone really reads this anyway.
I will just give you what I ran into today. First there was the same bug as
yesterday
only this time on 'Functions'
Can't locate object method "alias" via package "Database::Accessor::Function" at D:\GitHub\database-accessor-driver-dbi\lib/Database/Accessor/Driver/DBI.pm line 412.
Recently I have been working mostly on fixing bugs and making rakudo.js pass more roast tests.
While most of the fixed bugs affected one or a couple of tests recently fixing a longstanding closure deserialization bug and porting over a closure hack fixed a whole bunch of tests (as well us uncovered a bunch of easier to fix bug)
Some of the tests require implementing new features. A lot of them are fairly straightforward (like making a integer division by zero raise an exception).
An interesting/tricky one to implement where the native int8 and int16 types.
We emulate them by using a normal js number but for to emulate the overflow we use shifts.
For example for int8 we use: ($store_this_in_an_int8 << 24 >> 24).
I now plan to continue to work on fixing more bugs as there are still loads left (and maybe look into profiling and optimizing stuff as there are bunch of glaring inefficiencies
)
It is putter about some more day here in the Moose-Pen
I was puttering about today with my tests and I discovered something funny on some implications of SQL and it is to do with that 'AS' when playing with 'alias'. Now I knew it was an optional 'key-word' according to the SQL standard what I did not know is a number of DBs will syntax error when an optional key-word is used. So this SQL
SELECT sys_users.last_name AS last
FROM people AS sys_users
is correct to standard there are a number of DBs out there that only this will work
SELECT sys_users.last_name last
FROM people sys_users
That makes the above one almost 100% universal that I can tell. I originally wanted that 'AS' in there to make the generated SQL much more readable but I have come to realize that '99.9995%' of the time the end user Database::Accessor will never care what the end SQL is just that it works.
The London Perl Workshop is on Saturday 25th November, and as is traditional, the day will end with Lightning Talks, compèred by the inimitable Léon Brocard. In previous years things have been pretty fluid, with talks being accepted on the day. This year the deadline for Lightning Talk submissions is Monday 6th November, and we'll let prospective speakers know by Friday 10th.
If you've something to say, but not enough for 20 minutes, why not submit a 5 minute lightning talk?