module for checking taint peculiarities on some CPAN testers

Changes for 0.0.1 - 2024-03-25T03:15:44Z

• original version

SPVM Language

Changes for 0.989093 - 2023-03-25

• Bug Fix
• Internal Changes
• Test Cleanup

Add useful objects to your templates

Changes for 0.07 - 2024-03-24

• bump version

Simple backend-independent plotting for PDL

Changes for 1.010 - 2024-03-24

• fix PGPLOT to read devices correctly

Basic method declarations with signatures, without source filters

Changes for 1.14 - 2024-03-24

• Run number tests under C locale

PDL interface to the GNU Linear Programming Kit

Changes for 0.05 - 2024-03-24T12:33:00Z

• enforce C99 standard

create Perl client SDKs from OpenAPI specs

Changes for 0.01 - 2024-03-24

• Released on an unsuspecting world

Perl official company author's are being manipulated

https://www.youtube.com/watch?v=ZDk8y83lyAc
Perl official company author's are being manipulated

submitted by /u/todo_bem
[link] [comments]

Keep playing with Perl programming language authors upload server accounts .

^YouTube

Random hash type objects.

Changes for 0.05 - 2024-03-22T19:10:24+01:00

• Parameter 'num_generated' rewrite to use check_required().
• Update to Data::HashType@0.05 without 'active' parameter.

This is the explanation of what happened to Perl Author : INGENICO

https://www.youtube.com/watch?v=Qw-gBQHa3RY&list=LL&index=1

submitted by /u/todo_bem
[link] [comments]

The Official Perl programming language authors upload server and Perl Archive Network got hacked

The official Perl programming language authors upload server and and Perl Archive Network (cpan.org) got skipped by cranky stalker and here is a journey insi...

^YouTube

Locate and read records from human-edited data tables (Excel, CSV)

Changes for 0.013 - 2024-03-22

• Fix bug in unit tests causing failure when MRO::Compat not installed

Data objects for hash type.

Changes for 0.05 - 2024-03-22T17:25:32+01:00

• API CHANGE: Parameter 'active' is removed.
• API CHANGE: Parameter 'valid_from' is required.
• Fix dependencies.

CPAN.pm plugin for installing external dependencies

Changes for 0.77 - 2024-03-22

• support for rpm --whatprovides
• new test script rpm.t

Popping a selection list relative to a widget

Changes for 0.07

• fixed calculation of listbox height.

Random hash type objects.

Changes for 0.04 - 2024-03-22T16:08:10+01:00

• Add tests for valid_from.
• Regen documentation and example.

I've finally had some more time to do some real work related to perl.social again, and there was a recent question from someone again about me actually adopting a proper ToS/CoC there.

I'm not a lawyer so I've decided as a starting point that looking at similar communities out there and so I've grabbed the Mastodon CoC to start the discussion. I do not want to wholesale put anything into place without input from the community, so I'm going to start a discussion here and on perl.social (I'll edit a link to the post once I make it).

COC/TOS

Borrowing many things from the Mastodon CoC as a astarting point (https://github.com/mastodon/mastodon/blob/main/CODE_OF_CONDUCT.md).

I am removing a few things from it, not because I don't think they're good ideas or anything but also because I want to limit the scope of the initial discussion and the amount of work for myself as I'm still currently the only moderator but once the community there gets larger or it changes that I'm not the only one maintaining things, we will hold another discussion about everything.

I've changed a few things also, specifically to add stronger language that any moderators MUST document why an action was taken. This doesn't necessarily mean that I believe that those reasons must be immediately given to an affected user, but that they must be available when requested. Specifically I'm thinking of not informing in the context of bots, spam, illegal or otherwise legally actionable content (i.e. something that's going to get me a subpeona or court case).

Other proposed ideas: 1) Some kind of regular discussion, maybe annually? on ToS/CoC type things 1a) The idea being that we require a regular discussion of anything that's happened over the last time period to avoid it being possible for something happening being "swept under the rug" or "falling through the cracks" because it didn't get the proper time given to it previously. How this should be done I have no good recommendations for, likely creating a group on perl.social to host the conversation each time? 2) ?

Contributor Covenant Code of Conduct

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Privacy

I reserve the right to collect email or other identifiable contact information, and it will never be shared to an outside party without consent except in the case of it being required by some legal process. If at any time perl.social becomes a larger organization and there is a desire to change this, I will require the removal of all such information until explicit consent is given again with such a new policy. I don't know if there's a way I can make this legally enforcable but I see it as something I do not own and therefore cannot ethically give it to another party in that kind of scenario.

Both perl.social and I are located in the USA, and therefore I believe are not directly subject to the GDPR, but as there are similar laws in other jurisdictions even within the USA, and I basically agree with the ideas involved, I will do whatever is reasonable feasible to follow them.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

• Being respectful of differing opinions, viewpoints, and experiences
• Giving and gracefully accepting constructive feedback
• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
• Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

• The use of public and/or unwanted sexualized language or imagery, and sexual attention or advances of any kind. Consenting adults in private should be acceptable.
• Trolling, insulting or derogatory comments, and personal or political attacks
• Public or private harassment
• Publishing others' private information, such as a physical or email address, without their explicit permission
• Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and MUST communicate reasons for moderation decisions.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [hello@joinmastodon.org](mailto:hello@joinmastodon.org). All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

And from the Mastodon code of conduct available at https://github.com/mastodon/mastodon/blob/main/CODE_OF_CONDUCT.md

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

submitted by /u/simcop2387
[link] [comments]

GitHub - mozilla/inclusion: Our repository for Diversity, Equity and Inclusion work at Mozilla

Our repository for Diversity, Equity and Inclusion work at Mozilla - mozilla/inclusion

^GitHub

Data objects for login.

Changes for 0.03 - 2024-03-22T14:37:07+01:00

• API CHANGE: Add 'valid_from' and 'valid_to' parameters to Data::Login.
• API CHANGE: Add 'valid_from' and 'valid_to' parameters to Data::Login::Role. 'active' parameter will be removed in future. And 'valid_from' will be required in future.
• Add DESCRIPTION section to Data::Login doc.

BrowseEntry like widget without button

Changes for 0.02

• added -command option updated and corrected documentation

Utilities related to mineral supplements

Changes for 0.012 - 2024-03-22

• Add mg-mg-malate, mg-mg-malate-trihydrate.

General purpose command option wrapper

Changes for v0.99.1 - 2024-03-22T09:31:18Z

• Make tabstop configurable in -Mutil::filter module.

Implementation of various techniques used in data compression.

Changes for 0.03 - 2024-03-22

• ADDITIONS
• CHANGES

Plack search application.

Changes for 0.04 - 2024-03-21T14:13:15+01:00

• Add missing 'image_height' parameter description in doc.
• Add 'image_radius' parameter.
• Add 'name' attribute to search field.

Implementation of various techniques used in data compression.

Changes for 0.02 - 2024-03-21

• ADDITIONS
• CHANGES

ANSI sequence aware column command

Changes for 1.4101 - 2024-03-21T07:50:10Z

• make man page accurate

data pack for Business::ISBN

Changes for 20240321.001 - 2024-03-21T07:16:25Z

• Data update for 2024-03-21

Merges two users into the same effective user

Changes for 1.09 - 2024-03-20

• Do not try to load user from an empty email address
• Fix uninitialized warnings cased by undefined FIELD
• Only limit roles by id for valid users

IRS Form 1040 worksheets calculations

Changes for 0.05 - 2024-02-23T09:49:50Z

• In 0.04, pp_ssbw() wasn't doing any pretty-printing. Corrected.
• Like preceding versions, this version will probably not make it to CPAN, so I'm tagging it and pushing to GH

high-performance, selector-based, content-aware HTML template engine

Changes for 0.0901 - 2024-03-20

• fix a few typos in the documentation
• no functional changes

Problem- I have an apache application in which I am using mod_perl module. I want to log few things in a request lifecycle. I am able to do it across multiple files by calling get_logger("nameOfLogger"); and log to the hash that I am maintaining in my appender. But strangely there is one file in which when I call get_logger("nameOfLogger"); it no more has context of previous logs that I have captured before it in other files. What could be the possible cause. does this file needs to be in startup.pl ?

I would really appreciate the help and suggestions since I am stuck on this issue since a day

submitted by /u/FiredNeuron97
[link] [comments]

access GCC compiler builtin functions via XS

Changes for 0.03 - 2024-03-20

• Added more builtins. Added one test file for each builtin function supported. Created benchmarks comparing clz() XS vs PP. Enhanced documentation.

SPVM Language

Changes for 0.989089 - 2023-03-19

• Incompatible Changes
• Internal Changes

https://metacpan.org/recent is showing a reupload of perl-5.38.2 by user INGENICO.

submitted by /u/briang_
[link] [comments]

access GCC compiler builtin functions via XS

Changes for 0.01

• First version, released on an unsuspecting world.

Hey all!

As a recent graduate seeking a junior developer position, I received an invitation for a job interview which included a Perl coding exercise. How can i make my code better? Additionally, are there recommended best practices for documenting my progress on this exercise? I never programmed in perl, so bare with me. Thanks a lot!!

​

here's the task:

- read the data from a .csv file

- store data in one hash

- outputs the data as HTML, sorted by company and within the company by name

​

here is my code:

#!/usr/bin/perl use strict; use warnings; use Text::CSV; my $csv_file = 'Bewerbungstest.csv'; open(my $fh, '<', $csv_file) or die "Could not open file '$csv_file' $!"; my $csv = Text::CSV->new({ binary => 1 }) or die "Cannot use CSV: ".Text::CSV->error_diag(); $csv->header($fh); # Hash Wert my %data_hash; while (my $row = $csv->getline($fh)) { my $pid = $row->[0]; # PID as key my $company = $row->[1]; # Company name as key my $last_name = $row->[2]; # Employee last name my $first_name = $row->[3]; # Employee first name push @{$data_hash{$company}}, [$pid, $last_name, $first_name]; } close($fh); # Sort the company names alphabetically foreach my $company (sort keys %data_hash) { @{$data_hash{$company}} = sort {$a->[1] cmp $b->[1]} @{$data_hash{$company}}; } # HTML Output open(HTML, '>', 'output.html') or die "Could not open file: $!"; print HTML "<html>\n"; print HTML "<head>\n"; print HTML "<title>Employee List</title>\n"; print HTML "</head>\n"; print HTML "<body>\n"; print HTML "<h1>User Liste</h1>\n"; print HTML "<table border='1'>\n"; print HTML "<tr><th>PID</th><th>Company</th><th>Last Name</th><th>First Name</th>\n"; foreach my $company (sort keys %data_hash) { foreach my $entry (@{$data_hash{$company}}) { my ($pid, $last_name, $first_name,) = @$entry; print HTML "<tr>\n"; print HTML "<td>$pid</td>\n"; print HTML "<td>$company</td>\n"; print HTML "<td>$last_name</td>\n"; print HTML "<td>$first_name</td>\n"; print HTML "</tr>\n"; } } print HTML "</table>\n"; print HTML "</body>\n"; print HTML "</html>\n"; close(HTML); print "HTML file erfolgreich generiert\n"; 

submitted by /u/stayin_alive23
[link] [comments]

Data objects for login.

Changes for 0.02 - 2024-03-19T14:01:19+01:00

• Regen example file.
• Rewrite to new Data::HashType@0.04 with added 'valid_from' parameter.

Random hash type objects.

Changes for 0.03 - 2024-03-19T13:59:34+01:00

• Add support for Data::HashType@0.04.