view release on metacpan or search on metacpan
=head1 CONFIGURATION
You can save your configuration into C<~/.jenkins-cli.yml> so that you don't
have to enter them each time. The following is an example of what the file
looks like:
---
base_url: http://localhost:8080/
username: admin
password: my-secrent-password
view release on metacpan or search on metacpan
lib/App/JobLog/Log.pm view on Meta::CPAN
the portion of all logged notes falling within this interval. These
portions are represented as L<App::JobLog::Log::Note> objects.
=head2 find_previous
C<find_previous> looks for the logged event previous to a given
moment, returning the L<App::JobLog::Log::Event> objects and the
appropriate log line number, or the empty list if no such
event exists. It expects a L<DateTime> object as its parameter.
=head2 find_previous
C<find_previous> looks for the logged event previous to a given
moment, returning the L<App::JobLog::Log::Event> objects and the
appropriate log line number, or the empty list if no such
event exists. It expects a L<DateTime> object as its parameter.
=head2 append_event
view release on metacpan or search on metacpan
lib/App/KGB/Client/Git.pm view on Meta::CPAN
}
sub _describe_ref {
my( $self, $new ) = @_;
# raw commit looks like this:
#commit cc746cf3f6b8937c059cf6311a8903dba9936749
#tree 76bcae9bdbcfab304c8265d2c2cc245048c9f0f3
#parent 7e99c8b051169e43189c822c8db77bcad5956734
#author Damyan Ivanov <dmn@debian.org> 1257538837 +0200
#committer Damyan Ivanov <dmn@debian.org> 1257538837 +0200
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
kritika.fatpack view on Meta::CPAN
As this callback gets called less often then the C<filter_json_object>
one, decoding speed will not usually suffer as much. Therefore, single-key
objects make excellent targets to serialise Perl objects into, especially
as single-key JSON objects are as close to the type-tagged value concept
as JSON gets (it's basically an ID/VALUE tuple). Of course, JSON does not
support this in any way, so you need to make sure your data never looks
like a serialised Perl hash.
Typical names for the single object key are C<__class_whatever__>, or
C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even
things like C<__class_md5sum(classname)__>, to reduce the risk of clashing
kritika.fatpack view on Meta::CPAN
}
sub get_$name {
\$_[0]->{PROPS}->[$property_id] ? 1 : '';
}
/}}my$JSON;sub encode_json ($) {($JSON ||= __PACKAGE__->new->utf8)->encode(@_)}sub decode_json {($JSON ||= __PACKAGE__->new->utf8)->decode(@_)}sub to_json($) {Carp::croak ("JSON::PP::to_json has been renamed to encode_json.")}sub from_json(...
[\x00-\x7F]
|[\xC2-\xDF][\x80-\xBF]
|[\xE0][\xA0-\xBF][\x80-\xBF]
|[\xE1-\xEC][\x80-\xBF][\x80-\xBF]
|[\xED][\x80-\x9F][\x80-\xBF]
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/LXC/Container/Data/Debian.pm view on Meta::CPAN
sub package_of($$)
{
my ($self, $file) = @_;
$self->SUPER::package_of($file);
local $_;
# TODO: looks like pipe with redirection in shell never fails:
# uncoverable branch true
open my $dpkg, '-|', SEARCH . $file . ' 2>/dev/null'
or fatal('internal_error__1',
'error calling ' . SEARCH . $file . ': '. $!);
# escape special characters in file name:
view release on metacpan or search on metacpan
use App::Lazyd;
use YAML::Tiny;
unless (-f "$ENV{HOME}/.lazyd") {
die <<USAGE;
Please add a ~/.lazyd config file looks like this
username: foo
password: foo31337
USAGE
view release on metacpan or search on metacpan
lib/App/Lingua/BO/Wylie/Transliteration.pm view on Meta::CPAN
This merging process can be seen as building "ligatures", of which even more exist.
As we have seen, the vocal symbols (for all vocals except 'a', which is inherent)
need to be added in the proper places.
For the rest of the symbols that can be added, the scheme looks the following:
b s g r u b s
| | | | | | |
1 2 3 4 5 6 7
view release on metacpan or search on metacpan
lib/App/LintPrereqs.pm view on Meta::CPAN
use File::Which;
use Filename::Type::Backup qw(check_backup_filename);
use IPC::System::Options 'system', -log=>1;
use Module::CoreList::More;
use Proc::ChildError qw(explain_child_error);
use Scalar::Util 'looks_like_number';
use Sort::Sub qw(prereq_ala_perlancar);
use Version::Util qw(version_gt version_ne);
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2024-12-21'; # DATE
lib/App/LintPrereqs.pm view on Meta::CPAN
} else {
log_trace("Will assume perl %s (from running interpreter's \$^V)",
$^V);
if ($^V =~ /^v(\d+)\.(\d+)\.(\d+)/) {
$perlv = sprintf("%d\.%03d%03d", $1, $2, $3)+0;
} elsif (looks_like_number($^V)) {
$perlv = $^V;
} else {
return [500, "Can't parse \$^V ($^V)"];
}
}
view release on metacpan or search on metacpan
lib/App/ListRevDeps.pm view on Meta::CPAN
};
my @res;
for (ref($mod) eq 'ARRAY' ? @$mod : $mod) {
my $dist;
# if it already looks like a dist, skip an API call
if (/-/) {
$dist = $_;
} else {
my $modinfo = $chi->compute(
"metacpan-mod-$_", $ce, sub {
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
share/js/core/ajax.js view on Meta::CPAN
// The success and failure callbacks can be null or undefined, in which case App::MFILE::WWW will
// just display the status text in the #result div (i.e., the line at the bottom of the frame).
// If your AJAX calls needs any other handling than this, you need to provide at least a success
// callback.
//
// In all cases except login/logout, the MFILE AJAX Object looks like this:
// {
// "method": any HTTP method accepted by the backend server
// "path": valid path to backend server resource
// "body": content body to be sent to backend server (can be null)
// }
view release on metacpan or search on metacpan
lib/MHFS/EventLoop/Poll/Base.pm view on Meta::CPAN
use strict; use warnings;
use feature 'say';
use POSIX ":sys_wait_h";
use IO::Poll qw(POLLIN POLLOUT POLLHUP);
use Time::HiRes qw( usleep clock_gettime CLOCK_REALTIME CLOCK_MONOTONIC);
use Scalar::Util qw(looks_like_number);
use Data::Dumper;
use Devel::Peek;
#use Devel::Refcount qw( refcount );
use constant POLLRDHUP => 0;
view release on metacpan or search on metacpan
lib/App/MaMGal/EntryFactory.pm view on Meta::CPAN
my $path = shift;
# Do some path mangling in two special cases:
if ($path eq '.') {
# discover current directory name, so that it looks nice in
# listings, and we know where to ascend when retracting towards
# root directory
$path = Cwd::abs_path($path);
} elsif ($path eq '/') {
# mangle the path so that the following regular expression
view release on metacpan or search on metacpan
examples/rfc/README.pod view on Meta::CPAN
suitable for use in an EPUB, clean up the HTML file with this script in the
directory I<< examples/rfc >>.
bin/finish-htmlrfc.pl download/rfc2328.html > clean/rfc2328.html
This HTML-RFC looks exactly as the plain text version and is only suitable for
ebook readers with big screen because it does use the C<< <pre> >> tag to
render the text.
The alternative is to take the plaintext RFC and convert it like this
view release on metacpan or search on metacpan
lib/App/MarkFiles.pm view on Meta::CPAN
home directory. Once marked, files can be copied, moved, listed, or passed as
parameters to arbitrary shell commands.
This originated as a simple tool for collecting files from one or more
directories and moving or copying them to another. A basic usage pattern
looks something like this:
$ cd ~/screenshots
$ mark add foo.png
$ cd ~/blog/files/screenshots
$ mark mv
view release on metacpan or search on metacpan
lib/App/Math/Tutor/Cmd/Unit/Cmd/Cast.pm view on Meta::CPAN
use MooX::Options;
use Carp qw(croak);
use File::ShareDir ();
use Template ();
use Scalar::Util qw(looks_like_number);
has template_filename => (
is => "ro",
default => "twocols"
);
view release on metacpan or search on metacpan
lib/App/MechaCPAN/Deploy.pm view on Meta::CPAN
open my $snap_fh, '<', $file;
if ( my $line = <$snap_fh> !~ $snapshot_re )
{
die "File doesn't looks like a carton snapshot: $file";
}
my @stack = ($result);
my $prefix = '';
while ( my $line = <$snap_fh> )
view release on metacpan or search on metacpan
lib/App/MediaWiki2Git.pm view on Meta::CPAN
my $fn = $pagename;
write_file($fn, { atomic => 1 }, delete $props->{'*'});
my $author;
if ($props->{user} =~ m{^[0-9.:]+$}) {
# user looks like an IP address.
# exists $props->{anon} # looks promising, but broken in early
# revs (made with early mediawiki?)
$author = $self->anon2author($props->{user});
} else {
$author = sprintf('%s <%s>', ($props->{user}) x 2);
}