• 00:00 Introduction

• 01:30 OSDC Perl, mention last week

• 03:00 Nikolai Shaplov NATARAJ, one of our guests author of Lingua-StarDict-Writer on GitLab.

• 04:30 Nikolai explaining his goals about security memory leak in Net::SSLeay

• 05:58 What we did earlier. (Low hanging fruits.)

• 07:00 Let's take a look at the repository of Net::SSLeay

• 08:00 Try understand what happens in the repository?

• 09:15 A bit of explanation about adopting a module. (co-maintainer, unauthorized uploads)

• 11:00 PAUSE

• 15:30 Check the "river" status of the distribution. (reverse dependency)

• 17:20 You can CC-me in your correspondence.

• 18:45 Ask people to review your pull-requests.

• 21:30 Mention the issue with DBIx::Class and how to take over a module.

• 23:50 A bit about the OSDC Perl page.

• 24:55 CPAN Dashboard and how to add yourself to it.

• 27:40 Show the issues I opened asking author if they are interested in setting up GitHub Actions.

• 29:25 Start working on Dancer-Template-Mason

• 30:00 clone it

• 31:15 perl-tester Docker image.

• 33:30 Installing the dependencies in the Docker container

• 34:40 Create the GitHub Workflow file. Add to git. Push it out to GitHub.

• 40:55 First failure in the CI which is unclear.

• 42:30 Verifying the problem locally.

• 43:10 Open an issue.

• 58:25 Can you talk about dzil and Dist::Zilla?

• 1:02:25 We get back to working in the CI.

• 1:03:25 Add --notest to make installations run faster.

• 1:05:30 Add the git configuration to the CI workflow.

• 1:06:32 Is it safe to use --notest when installing dependencies?

• 1:11:05 git rebase squashing the commits into one commit

• 1:13:35 git push --force

• 1:14:10 Send the pull-request.

• 00:00 Introduction to OSDC
• 01:30 Introducing myself Perl Maven, Perl Weekly
• 02:10 The earlier issues.
• 03:10 How to select a project to contribute to?
• 04:50 Chat on OSDC Zulip
• 06:45 How to select a Perl project?
• 09:20 CPAN::Digger
• 10:10 Modules that don't have a link to their VCS.
• 13:00 Missing CI - GitHub Actions or GitLab Pipeline and Travis-CI.
• 14:00 Look at Term-ANSIEncode by Richard Kelsch - How to find the repository of this project?
• 15:38 Switching top look at Common-CodingTools by mistake.
• 16:30 How MetaCPAN knows where is the repository?
• 17:52 Clone the repository.
• 18:15 Use the szabgab/perl Docker container.
• 22:10 Run perl Makefile.PL, install dependency, run make and make distdir.
• 23:40 See the generated META.json file.
• 24:05 Edit the Makefile.PL
• 24:55 Explaining my method of cloning first (calling it origin) and forking later and calling that fork.
• 27:00 Really edit Makefile.PL and add the META_MERGE section and verify the generated META.json file.
• 29:00 Create a branch locally. Commit the change.
• 30:10 Create a fork on GitHub.
• 31:45 Add the fork as a remote repository and push the branch to it.
• 33:20 Linking to the PR on the OSDC Perl report page.
• 35:00 Planning to add .gitignore and maybe setting up GitHub Action.
• 36:00 Start from the main branch, create the .gitignore file.
• 39:00 Run the tests locally. Set up GitHub Actions to run the tests on every push.
• 44:00 Editing the GHA configuration file.
• 48:30 Commit, push to the fork, check the results of GitHub Action in my fork on GitHub.
• 51:45 Look at the version of the perldocker/perl-tester Docker image.
• 54:40 Update list of Perl versions in the CI. See the results on GitHub.
• 55:30 Show the version number of perl.

Organizations make it easier to have multiple maintainers and thus ensuring continuity of project, but it might also mean that none of the members really feel the urge to continue working on something.

In any case, I tried to collect all the Perl-related GitHub organizations.

Hopefully in ABC order...

• Beyond grep - It is mostly for ack, a better grep developed by Andy Lester. No public members. 4 repositories.

• Catalyst - Catalyst is a web-framework. Its runtime and various extensions are maintained in this organization. 10 members and 39 repositories.

• cpan-authors - A place for CPAN authors to collaborate more easily. 4 members and 9 repositories.

• davorg cpan - Organisation for maintaining Dave Cross's CPAN modules. No public members and 47 repositories.

• ExifTool - No public members. 3 repositories.

• Foswiki - The Foswiki and related projects. 13 members and 649 repositories.

• gitpan - An archive of CPAN modules - 2 members and 5k+ read-only repositories.

• Kelp framework - a web development framework. 1 member and 12 repositories.

• MetaCPAN - The source of the MetaCPAN site - 9 member and 56 rpositories.

• Mojolicious - Some Perl and many JavaScript projects. 5 members and 29 repositories.

• Moose - Moose,MooseX-*, Moo, etc. 11 members and 69 repositories.

• Netdisco - Netdisco and SNMP-Info projects. 10 members and 14 repositories.

• PadreIDE - Padre, the Perl IDE. 13 members and 102 repositories.

• Paracamelus - No public members. 2 repositories.

• Perl - Perl 5 itself, Docker images, etc. 20 members, 8 repositories.

• Perl Actions - GitHub Actions to be used in workflows. 5 members and 9 repositories.

• Perl Advent Calendar - including the source of perl.com. 3 members and 8 repositories.

• Perl Bitcoin - Perl Bitcoin Toolchain Collective. 3 members and 7 repositories.

• Perl Toolchain Gang - ExtUtils::MakeMaker, Module::Build, etc. 27 members and 41 repositories.

• Perl Tools Team - source of planetperl , perl-ads etc. No public members. 6 repositories.

• Perl Dancer - Dancer, Dancer2, many plugins. 30 members and 79 repositories.

• perltidy - Only for Perl::Tidy. No public members. 1 repository.

• perl5-dbi - DBI, several DBD::* modules, and some related modules. 7 members and 15 repositories.

• perl.org - also cpan.org and perldoc.perl.org. 3 members and 7 repositories.

• Perl5 - DBIx-Class and DBIx-Class-Historic. No public members. 2 repositories.

• perl5-utils - List::MoreUtils, File::ShareDir etc. 2 members and 22 repositories.

• Perl-Critic - PPI, Perl::Critic and related. 7 members and 5 repositories.

• perl-ide - Perl Development Environments. 26 members and 13 repositories.

• perl-pod - Pod::Simple, Test::Pod. 1 member and 4 repositories.

• PkgConfig - 1 member 1 repository.

• plack - psgi-specs, Plack and a few middlewares. 5 members and 7 repositories.

• RexOps - Rex, Rexify and related projects. 1 member and 46 repositories.

• Sqitch - Sqitch for Sensible database change management and related projects. No public members. 16 repositories.

• StrawberryPerl - The Perl distribution for MS Windows. 4 members and 10 repositories.

• Test-More - Test::Builder, Test::Simple, Test2 etc. - 4 members, 27 repositories.

• The Enlightened Perl Organisation - Task::Kensho and Task::Kensho::*. 1 member and 1 repository.

• Thunderhorse Framework - a modern web development framework. No public members. 4 repositories.

• Webmin - Webmin is a web-based system administration tool for Unix-like servers. - 5 repositories.

Companies

These are bot Perl-specific GitHub organizations, but some of the repositories are in Perl.

• cPanel - Open Source Software provided by cPanel. 1 member and 22 repositories.

• DuckDuckGo - The search engine. 19 members and 122 repositories.

• Fastmail - Open-source software developed at Fastmail. 4 members and 38 repositories.

• RotherOSS - Otobo (OTRS fork). No public members. 47 repositories.

You can lock_hash and later you can unlock_hash if you'd like to make some changes to it.

In this example you can see 3 different actions commented out. Each one would raise an exception if someone tries to call them on a locked hash. After we unlock the hash we can execute those actions again.

I tried this both in perl 5.40 and 5.42.

examples/locking_hash.pl

use strict;
use warnings;
use feature 'say';

use Hash::Util qw(lock_hash unlock_hash);
use Data::Dumper qw(Dumper);


my %person = (
    fname => "Foo",
    lname => "Bar",
);
lock_hash(%person);

print Dumper \%person;
print "$person{fname} $person{lname}\n";
say "fname exists ", exists $person{fname};
say "language exists ", exists $person{language};

# $person{fname} = "Peti";     # Modification of a read-only value attempted
# delete $person{lname};       # Attempt to delete readonly key 'lname' from a restricted hash
# $person{language} = "Perl";  # Attempt to access disallowed key 'language' in a restricted hash

unlock_hash(%person);

$person{fname} = "Peti";     # Modification of a read-only value attempted
delete $person{lname};       # Attempt to delete readonly key 'lname' from a restricted hash
$person{language} = "Perl";  # Attempt to access disallowed key 'language' in a restricted hash

print Dumper \%person;

$VAR1 = {
          'lname' => 'Bar',
          'fname' => 'Foo'
        };
Foo Bar
fname exists 1
language exists
$VAR1 = {
          'language' => 'Perl',
          'fname' => 'Peti'
        };

• 00:00 Working with Peter Nilsson

• 00:01 Find a module to add GitHub Action to. go to CPAN::Digger recent

• 00:10 Found Tree-STR

• 01:20 Bug in CPAN Digger that shows a GitHub link even if it is broken.

• 01:30 Search for the module name on GitHub.

• 02:25 Verify that the name of the module author is the owner of the GitHub repository.

• 03:25 Edit the Makefile.PL.

• 04:05 Edit the file, fork the repository.

• 05:40 Send the Pull-Request.

• 06:30 Back to CPAN Digger recent to find a module without GitHub Actions.

• 07:20 Add file / Fork repository gives us "unexpected error".

• 07:45 Direct fork works.

• 08:00 Create the .github/workflows/ci.yml file.

• 09:00 Example CI yaml file copy it and edit it.

• 14:25 Look at a GitLab CI file for a few seconds.

• 14:58 Commit - change the branch and add a description!

• 17:31 Check if the GitHub Action works properly.

• 18:17 There is a warning while the tests are running.

• 21:20 Opening an issue.

• 21:48 Opening the PR (on the wrong repository).

• 22:30 Linking to output of a CI?

• 23:40 Looking at the file to see the source of the warning.

• 25:25 Assigning an issue? In an open source project?

• 27:15 Edit the already created issue.

• 28:30 USe the Preview!

• 29:20 Sending the Pull-Request to the project owner.

• 31:25 Switching to Jonathan

• 33:10 CPAN Digger recent

• 34:00 Net-SSH-Perl of BDFOY - Testing a networking module is hard and Jonathan is using Windows.

• 35:13 Frequency of update of CPAN Digger.

• 36:00 Looking at our notes to find the GitHub account of the module author LNATION.

• 38:10 Look at the modules of LNATION on MetaCPAN

• 38:47 Found JSON::Lines

• 39:42 Install the dependencies, run the tests, generate test coverage.

• 40:32 Cygwin?

• 42:45 Add Github Action copying it from the previous PR.

• 43:54 META.yml should not be committed as it is a generated file.

• 48:25 I am looking for sponsors!

• 48:50 Create a branch that reflects what we do.

• 51:38 commit the changes

• 53:10 Fork the project on GitHub and setup git remote locally.

• 55:05 git push -u fork add-ci

• 57:44 Sending the Pull-Request.

• 59:10 The 7 dwarfs and Snowwhite. My hope is to have a 100 people sending these PRs.

• 1:01:30 Feedback.

• 1:02:10 Did you think this was useful?

• 1:02:55 Would you be willing to tell people you know that you did this and you will do it again?

• 1:03:17 You can put this on your resume. It means you know how to do it.

• 1:04:16 ... and Zoom suddenly closed the recording...

• 00:00 Introduction and about OSDC Perl
• 01:50 Sponsors of MetaCPAN, looking at some modules on CPAN.
• 03:30 The river status
• 04:10 Picking MIME::Lite and looking at MetaCPAN. Uses RT, has no GitHub Actions.
• 05:55 Look at the clone of the repository, the 2 remotes and the 3 branches.
• 06:40 GitHub Actions Examples
• 08:00 Running the Docker container locally. Install the dependencies.
• 09:10 Run the tests locally.
• 09:20 Add the .gitignore file.
• 10:30 Picking a module from MetaCPAN recent
• 11:10 CPAN Digger recent
• 12:20 Explaining about pair-programming and workshop.
• 13:25 CPAN Digger statistics
• 14:15 Generate test coverage report using Devel::Cover.
• 17:15 The fold function that is not tested and not even used.
• 18:39 Wanted to open an issue about fold, but I'll probbaly don't do it on RT.
• 20:00 Updating the OSDC Perl document with the TODO items.
• 21:13 Split the packages into files?
• 22:27 The culture of Open Source contributions.
• 24:20 Why is the BEGIN line red when the content of the block is green?
• 27:40 Switching to the long-header branch.
• 30:40 Finding header_as_string in the documentation.
• 32:15 Going over the test with the long subject line.
• 33:54 Let's compare the result to an empty string.
• 36:15 Switching to Test::Longstring to see the difference.
• 37:35 Test::Differences was also suggested.
• 39:40 Push out the branch and send the Pull-request.
• 40:35 Did this really increase the test coverage? Let's see it.
• 43:50 Messing up the explanation about codition coverage.
• 45:35 The repeated use of the magic number 72.
• 47:00 Is the output actually correct? Is it according to the standard?
• 51:45 Discussion about /usr/bin/perl on the first line.
• 52:45 No version is specified.
• 55:15 The sentence should be "conforms to the standard"

This example is based on the one in the documentation of the JSON::Schema::Validate and tweaked a bit. It will be useful again if we continue dealing with this module.

examples/json_schema_validate.pl

use JSON::Schema::Validate;
use JSON ();
use open qw( :std :encoding(UTF-8) );
my $schema = {
    '$schema' => 'https://json-schema.org/draft/2020-12/schema',
    '$id'     => 'https://example.org/s/root.json',
    type      => 'object',
    required  => [ 'name' ],
    properties => {
        name => { type => 'string', minLength => 5 },
        next => { '$dynamicRef' => '#Node' },
    },
    '$dynamicAnchor' => 'Node',
    additionalProperties => JSON::false,
};
my $js = JSON::Schema::Validate->new( $schema )
    ->compile
    ->content_checks
    ->ignore_unknown_required_vocab
    ->prune_unknown
    ->register_builtin_formats
    ->trace
    ->trace_limit(200) # 0 means unlimited
    ->unique_keys; # enable uniqueKeys

    #my $data = {
    #    name => 'head',
    #    next => {
    #        name => 'tail'
    #    }
    #};
    #my $data = {
    #    name => 23,
    #    next => {
    #        name => 'tail'
    #    }
    #};
    #my $data = {
    #    name => 'head',
    #};
my $data = {
    name => 'head big',
};


my $ok = $js->validate($data)
    or die( $js->error );
print "ok\n";

Actually "Now" was a while ago, since then I upgraded Ubuntu and now I get all kinds of other error messages.

However, I wonder.

Why are there so many errors?

Who's fault is it?

• A failure of the Perl community?

• A failure of the Ubuntu or the Debian developers?

• A failure of the whole idea of Open Source?

• Maybe I broke the system?

It starts so badly and then it crashes. I don't want to spend time figuring out what is the problem. I don't even have the energy to open a ticket. I am not even sure where should I do it. On Ubuntu? On the Shutter project?

Here is the output:

$ shutter
Subroutine Pango::Layout::set_text redefined at /usr/share/perl5/Gtk3.pm line 2299.
	require Gtk3.pm called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
Subroutine Pango::Layout::set_markup redefined at /usr/share/perl5/Gtk3.pm line 2305.
	require Gtk3.pm called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.36/Glib/Object/Introspection.pm line 110.
 at /usr/share/perl5/Gtk3.pm line 489.
	Gtk3::import("Gtk3", "-init") called at /usr/bin/shutter line 72
	Shutter::App::BEGIN() called at /usr/bin/shutter line 72
	eval {...} called at /usr/bin/shutter line 72
Variable "$progname_active" will not stay shared at /usr/bin/shutter line 2778.
Variable "$progname" will not stay shared at /usr/bin/shutter line 2779.
Variable "$im_colors_active" will not stay shared at /usr/bin/shutter line 2787.
Variable "$combobox_im_colors" will not stay shared at /usr/bin/shutter line 2788.
Variable "$trans_check" will not stay shared at /usr/bin/shutter line 2798.


... About 700 similar error messages ...


Name "Gtk3::Gdk::SELECTION_CLIPBOARD" used only once: possible typo at /usr/bin/shutter line 291.
WARNING: gnome-web-photo is missing --> screenshots of websites will be disabled!

 at /usr/bin/shutter line 9038.
	Shutter::App::fct_init_depend() called at /usr/bin/shutter line 195
Useless use of hash element in void context at /usr/share/perl5/Shutter/App/Common.pm line 77.
	require Shutter/App/Common.pm called at /usr/bin/shutter line 206
Useless use of hash element in void context at /usr/share/perl5/Shutter/App/Common.pm line 80.
	require Shutter/App/Common.pm called at /usr/bin/shutter line 206
Subroutine lookup redefined at /usr/share/perl5/Shutter/Draw/DrawingTool.pm line 28.
	require Shutter/Draw/DrawingTool.pm called at /usr/bin/shutter line 228
Variable "$self" will not stay shared at /usr/share/perl5/Shutter/Draw/DrawingTool.pm line 671.
	require Shutter/Draw/DrawingTool.pm called at /usr/bin/shutter line 228
Variable "$self" will not stay shared at /usr/share/perl5/Shutter/Screenshot/SelectorAdvanced.pm line 840.
	require Shutter/Screenshot/SelectorAdvanced.pm called at /usr/bin/shutter line 233
Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

• SVG the module for which we wrote tests.

• Devl-Cover to generate test coverage report run cover -test.

• Test::More

• Test::Exception

• done_testing() or done_testing(2)

• CPAN cover

Meeting summary

Quick recap

The meeting began with informal introductions and discussions about Perl programming, including experiences with maintaining Perl codebases and the challenges of the language's syntax. The main technical focus was on testing and code coverage, with detailed demonstrations of using Devel::Cover and various testing modules in Perl, including examples of testing SVG functionality and handling exceptions. The session concluded with discussions about testing practices, code coverage implementation, and the benefits of automated testing, while also touching on practical aspects of Perl's object-oriented programming and error handling features.

SVG Test Coverage Analysis

Gabor demonstrated how to use Devel::Cover to generate test coverage reports for the SVG.pm module. He showed that the main module has 98% coverage, while some submodules have lower coverage. Gabor explained how to interpret the coverage reports, including statement, branch, and condition coverage. He also discussed the importance of identifying and removing unused code that appears uncovered by tests. Gabor then walked through some example tests in the SVG distribution, explaining how they verify different aspects of the SVG module's functionality.

Original announcement

Adding tests to legacy Perl code

During this live coding event we'll take a Perl module from CPAN and add some tests to it.

Further events

Register on the Perl Maven Luma calendar.

Next

• 2025.12.01 Perl Code-reading and testing

Past

• 2024.06.13 Getting Started with Docker for Perl Developers

• 2024.08.04 GitHub Actions for Perl projects

• 2024.08.15 GitHub pages for Perl developers

• 2025.01.20 GitLab pipelines and CI for Perl developers

• 2025.11.11 Adding tests to legacy Perl code

Ideas for further sessions

• Perl Code-reading and testing: We are going to try fuzz-testing using the https://metacpan.org/dist/App-Test-Generator
• Dancer2 themes (new features in Dancer2 version 2)
• modern coding practices like the new features of Perl 5.38+
• named arguments
• maybe also HTMX
• Bioinformatics-related things.