busy results from the CPAN

lib/Dist/Zilla/Plugin/MinimumPerl.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-Plugin-Pinto-Add

2 results

lib/Dist/Zilla/Plugin/Pinto/Add.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-Plugin-Test-UseAllModules

2 results

lib/Dist/Zilla/Plugin/Test/UseAllModules.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-PluginBundle-Apocalyptic

2 results

lib/Dist/Zilla/PluginBundle/Apocalyptic.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-PluginBundle-Author-BBYRD

3 results

lib/Dist/Zilla/PluginBundle/Author/BBYRD.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-PluginBundle-Author-TABULO

2 results

Notes/cpan-namespaces/cpan-namespaces-L1-L3.txt view on Meta::CPAN

Net::ICal::Attendee
Net::ICal::Daylight
Net::ICal::Duration
Net::ICal::ETJ
Net::ICal::Event
Net::ICal::Freebusy
Net::ICal::FreebusyItem
Net::ICal::Journal
Net::ICal::Period
Net::ICal::Recurrence
Net::ICal::Standard
Net::ICal::Time

view all matches for this distribution

Dist-Zilla-PluginBundle-Prereqs

3 results

lib/Dist/Zilla/PluginBundle/Prereqs.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-Role-MetaCPANInterfacer

3 results

lib/Dist/Zilla/Role/MetaCPANInterfacer.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-Role-PluginBundle-Merged

3 results

lib/Dist/Zilla/Role/PluginBundle/Merged.pm view on Meta::CPAN


=head2 Internet Relay Chat

You can get live help by using IRC ( Internet Relay Chat ). If you don't know what IRC is,
please read this excellent guide: L<http://en.wikipedia.org/wiki/Internet_Relay_Chat>. Please
be courteous and patient when talking to us, as we might be busy or sleeping! You can join
those networks/channels and get help:

=over 4

=item *

view all matches for this distribution

Dist-Zilla-TravisCI

3 results

README view on Meta::CPAN

 Internet Relay Chat

    You can get live help by using IRC ( Internet Relay Chat ). If you
    don't know what IRC is, please read this excellent guide:
    http://en.wikipedia.org/wiki/Internet_Relay_Chat. Please be courteous
    and patient when talking to us, as we might be busy or sleeping! You
    can join those networks/channels and get help:

      * irc.perl.org

      You can connect to the server at 'irc.perl.org' and talk to this

view all matches for this distribution

DocSet

2 results

examples/site/src/docs/2.0/os/win32/install.pod view on Meta::CPAN


As described in the discussion of issues in L<multithreaded
win32|docs::1.0::os::win32::multithread>, a mod_perl 1.0 enabled server
based on Apache 1.3 on Win32 is limited to a single thread serving a
request at a time. This effectively prevents concurrent processing,
which can have serious implications for busy sites. This problem is
addressed in the multi-thread/multi-process approach of mod_perl
2.0/Apache 2.0.  This document discusses how to obtain mod_perl 2.0.

=head1 Installing

view all matches for this distribution

Docker-Client

16 results

              Author: ""
              Created: "2015-09-10T08:30:53.26995814Z"
              GraphDriver:
                Name: "aufs"
              RepoDigests:
                - "localhost:5000/test/busybox/example@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf"
              RepoTags:
                - "example:1.0"
                - "example:latest"
                - "example:stable"
              Config:

              Images:
                -
                  Id: "sha256:2b8fd9751c4c0f5dd266fcae00707e67a2545ef34f9a29354585f93dac906749"
                  ParentId: ""
                  RepoTags:
                    - "busybox:latest"
                  RepoDigests:
                    - "busybox@sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6"
                  Created: 1466724217
                  Size: 1092588
                  SharedSize: 0
                  VirtualSize: 1092588
                  Labels: {}

              Containers:
                -
                  Id: "e575172ed11dc01bfce087fb27bee502db149e1a0fad7c296ad300bbff178148"
                  Names:
                    - "/top"
                  Image: "busybox"
                  ImageID: "sha256:2b8fd9751c4c0f5dd266fcae00707e67a2545ef34f9a29354585f93dac906749"
                  Command: "top"
                  Created: 1472592424
                  Ports: []
                  SizeRootFs: 1092588

              - type: "object"
                example:
                  Name: "top"
                  TaskTemplate:
                    ContainerSpec:
                      Image: "busybox"
                      Args:
                        - "top"
                    Resources:
                      Limits: {}
                      Reservations: {}

view all matches for this distribution

Docker-Names-Random

2 results

lib/Docker/Names/Random.pm view on Meta::CPAN

I<interesting_mendeleev>,
I<epic_engelbart>,
I<lucid_dhawan>,
I<recursing_cori>,
I<ecstatic_liskov> and
I<busy_ardinghelli>.

The combination I<boring_wozniak> is not allowed because
L<Steve Wozniak|https://en.wikipedia.org/wiki/Steve_Wozniak> is not boring.
This same limitation exists in the
L<original code|https://github.com/moby/moby/blob/master/pkg/namesgenerator/names-generator.go>.

lib/Docker/Names/Random.pm view on Meta::CPAN

- word: beautiful
- word: blissful
- word: bold
- word: boring
- word: brave
- word: busy
- word: charming
- word: clever
- word: cool
- word: compassionate
- word: competent

view all matches for this distribution

Doxygen-Lua

1 match

example/Doxyfile view on Meta::CPAN

# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
# determine which symbols to keep in memory and which to flush to disk.
# When the cache is full, less often used symbols will be written to disk.
# For small to medium size projects (<1000 input files) the default value is
# probably good enough. For larger projects a too small cache size can cause
# doxygen to be busy swapping symbols to and from disk most of the time
# causing a significant performance penality.
# If the system has enough physical memory increasing the cache will improve the
# performance by keeping more symbols in memory. Note that the value works on
# a logarithmic scale so increasing the size by one will rougly double the
# memory usage. The cache size is given by this formula:

view all matches for this distribution

DynGig-Util

1 match

lib/DynGig/Util/MultiPhase.pm view on Meta::CPAN


=cut
sub run
{
    my ( $this, %param ) = @_;
    my ( %busy, %retry, %error, %thread );
    my $retry = $this->{retry};
    my $thread = $this->{thread};
    my %dst = %{ $this->{dst} };
    my %src = %{ $this->{src} };
    my $queue = Thread::Queue->new();

lib/DynGig/Util/MultiPhase.pm view on Meta::CPAN

            {
                $retry{$dst} ||= 0;

                if ( $retry{$dst} < $retry )
                {
                    $dst{$dst} = $busy{$dst};
                    $retry{$dst} ++;
                }
                else
                {
                    $error{$dst} = $result;
                }
            }
            else
            {
                $src{$dst} = $busy{$dst};
            }

            $src{$src} = $busy{$src};

            delete $busy{$src};
            delete $busy{$dst};

            $thread{$src}{$dst}->join();

            print $handle "$src => $dst $result";
        }

lib/DynGig/Util/MultiPhase.pm view on Meta::CPAN

        {
            last unless keys %src && keys %dst;

            my ( $src, $dst ) = $this->_select( \%src, \%dst );

            $busy{$src} = $src{$src};
            $busy{$dst} = $dst{$dst};

            delete $src{$src};
            delete $dst{$dst};

            $thread{$src}{$dst} = threads::async

view all matches for this distribution

EAFDSS

6 results

lib/EAFDSS.pm view on Meta::CPAN

   0x09: Printing type bad
   0x0A: Cannot execute with day open
   0x0B: RTC programming requires jumper
   0x0C: RTC date or time invalid
   0x0D: No records in fiscal period
   0x0E: Device is busy in another task
   0x0F: No more header records allowed
   0x10: Cannot execute with block open
   0x11: Block not open
   0x12: Bad data stream
   0x13: Bad signature field

view all matches for this distribution

EBook-Generator

1 match

t/Makefile view on Meta::CPAN

	./website2ebook.pl http://secrethistoryofstarwars.com/
	./website2ebook.pl http://www.paulgraham.com/13sentences.html
	./website2ebook.pl http://rigaux.org/language-study/syntax-across-languages.html
	./website2ebook.pl http://www.math.tamu.edu/~cyan/Rota/mitless.html
	./website2ebook.pl http://designmatrix.wordpress.com/2009/08/12/10-signs-of-intellectual-honesty-3/
	./website2ebook.pl http://zenhabits.net/the-essential-time-saving-guide-for-busy-people/
	./website2ebook.pl http://pewresearch.org/pubs/1623/future-cloud-computing-technology-experts
	./website2ebook.pl http://www.wilshipley.com/blog/2008/07/pimp-my-code-part-15-greatest-bug-of.html
	./website2ebook.pl http://blog.wolfram.com/2008/12/01/the-incredible-convenience-of-mathematica-image-processing/
	./website2ebook.pl http://www.dirjournal.com/info/most-dangerous-roads-in-the-world/
	./website2ebook.pl http://zenhabits.net/the-only-guide-to-happiness-youll-ever-need/

view all matches for this distribution

EBook-Tools

3 results

MANIFEST view on Meta::CPAN

t/test-part1.html
t/test-part2.html
t/test-containsmetadata.html
t/testopf-emptyuid.xml
t/testopf-missingfwid.xml
t/toobusy.jpg
t/imp/README.txt
t/imp/REBtestdoc-ETI.RES/BEDO
t/imp/REBtestdoc-ETI.RES/BYVI
t/imp/REBtestdoc-ETI.RES/DATA.FRK
t/imp/REBtestdoc-ETI.RES/DCXK

view all matches for this distribution

EOL

1 match

  where a man could hide.  Men much relieved when search over, and
  went back to work cheerfully.  First mate scowled, but said
  nothing.


  22 July.--Rough weather last three days, and all hands busy
  with sails, no time to be frightened.  Men seem to have
  forgotten their dread.  Mate cheerful again, and all on
  good terms.  Praised men for work in bad weather.  Passed
  Gibraltar and out through Straits.  All well.

bad enough to lose, and if they delayed they would sacrifice Miss
Lucy.  So, sobbing and crying they went about their way, half clad as
they were, and prepared fire and water.  Fortunately, the kitchen and
boiler fires were still alive, and there was no lack of hot water.  We
got a bath and carried Lucy out as she was and placed her in it.
Whilst we were busy chafing her limbs there was a knock at the hall
door.  One of the maids ran off, hurried on some more clothes, and
opened it.  Then she returned and whispered to us that there was a
gentleman who had come with a message from Mr. Holmwood.  I bade her
simply tell him that he must wait, for we could see no one now.  She
went away with the message, and, engrossed with our work, I clean

from both my bedroom and the drawing room I can see the
great elms of the cathedral close, with their great black
stems standing out against the old yellow stone of the cathedral,
and I can hear the rooks overhead cawing and cawing and
chattering and chattering and gossiping all day, after the manner
of rooks--and humans.  I am busy, I need not tell you, arranging
things and housekeeping.  Jonathan and Mr. Hawkins are busy all
day, for now that Jonathan is a partner, Mr. Hawkins wants to
tell him all about the clients.

"How is your dear mother getting on?  I wish I could run up
to town for a day or two to see you, dear, but I dare not

cargo of the Count's to its place in London.  Later, we may be able to
deal with it.  Billington junior, a nice lad, met me at the station,
and brought me to his father's house, where they had decided that I
must spend the night.  They are hospitable, with true Yorkshire
hospitality, give a guest everything and leave him to do as he likes.
They all knew that I was busy, and that my stay was short, and Mr.
Billington had ready in his office all the papers concerning the
consignment of boxes.  It gave me almost a turn to see again one of
the letters which I had seen on the Count's table before I knew of his
diabolical plans.  Everything had been carefully thought out, and done
systematically and with precision.  He seemed to have been prepared

took ill, and Quincey is more like his own bright self than he has
been for many a long day.

Van Helsing stepped from the carriage with the eager nimbleness of a
boy.  He saw me at once, and rushed up to me, saying, "Ah, friend
John, how goes all?  Well?  So!  I have been busy, for I come here to
stay if need be.  All affairs are settled with me, and I have much to
tell.  Madam Mina is with you?  Yes.  And her so fine husband?  And
Arthur and my friend Quincey, they are with you, too?  Good!"

As I drove to the house I told him of what had passed, and of how my


1 October, 4 A.M.--Just as we were about to leave the house, an urgent
message was brought to me from Renfield to know if I would see him at
once, as he had something of the utmost importance to say to me.  I
told the messenger to say that I would attend to his wishes in the
morning, I was busy just at the moment.

The attendant added, "He seems very importunate, sir.  I have never
seen him so eager.  I don't know but what, if you don't see him soon,
he will have one of his violent fits."  I knew the man would not have
said this without some cause, so I said, "All right, I'll go now," and

speak of anything that has happened.  I rest on the sofa, so as not to
disturb her.


1 October, later.--I suppose it was natural that we should have all
overslept ourselves, for the day was a busy one, and the night had no
rest at all.  Even Mina must have felt its exhaustion, for though I
slept till the sun was high, I was awake before her, and had to call
two or three times before she awoke.  Indeed, she was so sound asleep
that for a few seconds she did not recognize me, but looked at me with
a sort of blank terror, as one looks who has been waked out of a bad

view all matches for this distribution

ETLp

1 match

lib/ETLp/Manual/Install.pod view on Meta::CPAN

   4. Perform the user request
   5. Exit
   
=back

With small applications on a non-busy site, this shouldn't cause any issues. However, it doesn't scale very well. Although ETLp Runtime Audit Browser isn't especially busy, it does requite many dependent classes.  In order to mitigate the issues abov...

=over 4

   1. When the first request is received, the Persistent Perl interpreter is launched.
   2. The code is compiled and a connection is made to the database.

view all matches for this distribution

EV-ClickHouse

6 results

eg/pool.pl view on Meta::CPAN

#!/usr/bin/env perl
# Connection pool: fan out N concurrent queries through a fixed pool.
# Pool->_pick chooses the least-busy connection; ties round-robin.
use strict;
use warnings;
use EV;
use EV::ClickHouse;

view all matches for this distribution

EV-Gearman

1 match

src/EV__Gearman.xs view on Meta::CPAN

    if (self->worker_sleeping) return;
    self->worker_sleeping = 1;
    enqueue_packet(aTHX_ self, GM_CMD_PRE_SLEEP, NULL, 0, NULL);
}

/* Drive the worker loop forward: if active and not busy, GRAB. */
static void worker_continue(pTHX_ ev_gm_t *self) {
    if (!self->worker_active || !self->connected) return;
    if (self->worker_grab_inflight || self->worker_sleeping) return;
    if (ngx_queue_empty(&self->functions)) return;
    worker_send_grab(aTHX_ self);

view all matches for this distribution

EV-Loop-Async

2 results

Async.pm view on Meta::CPAN


=head1 DESCRIPTION

This module implements a rather specialised event loop - it takes a normal
L<EV> event loop and runs it in a separate thread. That means it will poll
for events even while your foreground Perl interpreter is busy (you don't
need to have perls pseudo-threads enabled for this either).

Whenever the event loop detecs new events, it will interrupt perl and ask
it to invoke all the pending watcher callbacks. This invocation will be
"synchronous" (in the perl thread), but it can happen at any time.

Async.pm view on Meta::CPAN

instantaneous, or take a few hours).

No locking is required.

Example: lock the loop, create a timer, nudge the loop so it takes notice
of the new timer, then evily busy-wait till the timer fires.

   my $timer;
   my $flag;

   {

view all matches for this distribution

EV-MariaDB

1 match

lib/EV/MariaDB.pm view on Meta::CPAN

executing it. Required before C<send_long_data>. Types are detected
the same way as in C<execute>.

Dies with C<"another operation is in progress"> or
C<"cannot bind while pipeline results are pending"> when invoked on a
busy connection.

=head2 reset

    $m->reset;

view all matches for this distribution

EV-Pg

1 match

Pg.xs view on Meta::CPAN

                            handle_conn_loss(self);
                            return;
                        }
                        /* ce == 0: END queued, flush pending; ce > 0: END sent.
                         * asyncStatus is already PGASYNC_BUSY â€” fall through to
                         * drain COMMAND_OK (or set draining_single_row if busy). */
                        check_flush(self);
                        if (self->magic != EV_PG_MAGIC || !self->conn) {
                            if (last_res) PQclear(last_res);
                            return;
                        }

view all matches for this distribution

EV-Websockets

1 match

Websockets.xs view on Meta::CPAN

   means "service as soon as possible". This timer only paces lws's time-based
   work (connection/handshake timeouts, TLS cert aging, draining buffered rx) --
   socket readability/writability is driven by the per-fd io watcher, not here.
   We deliberately floor the delay at 1ms rather than arming an ev_idle watcher
   on 0: do_lws_service is now non-blocking, so an always-ready idle watcher
   would busy-spin at 100% CPU whenever lws keeps asking for immediate service.
   A 1ms floor lets the loop block briefly so every other EV watcher still
   fires, at negligible latency for this coarse, time-based work. */
static void schedule_timeout(ev_ws_ctx_t* ctx) {
    int delay_ms = lws_service_adjust_timeout(ctx->lws_ctx, 1000, 0);
    double delay_s;

view all matches for this distribution

EV-cares

2 results

lib/EV/cares.pm view on Meta::CPAN

        });
    }
    return;
}

# is_busy: true iff there are pending queries on this resolver.  Cheap
# wrapper for the most common active_queries comparison.
sub is_busy { $_[0]->active_queries > 0 }

# wait_idle($timeout_seconds): pump the EV loop until either all of this
# resolver's pending queries complete or the timeout elapses.  Returns
# true if the channel drained, false on timeout.  Useful in mostly-
# synchronous scripts that want to ensure callbacks have run before

lib/EV/cares.pm view on Meta::CPAN

C<destroy>; returns C<0> in that case (during interpreter global
destruction the count may reflect whatever was pending, since
C<ares_destroy> is intentionally skipped on the global-destruction
path).

=head2 is_busy

    if ($r->is_busy) { ... }

Convenience wrapper for C<< $r->active_queries > 0 >>.

=head2 wait_idle

view all matches for this distribution

EV

1 match

but if that fails, expect a fairly low limit on the number of fds when
using this backend. It doesn't scale too well (O(highest_fd)), but its
usually the fastest backend for a low number of (low-numbered :) fds.

To get good performance out of this backend you need a high amount of
parallelism (most of the file descriptors should be busy). If you are
writing a server, you should C<accept ()> in a loop to accept as many
connections as possible during one iteration. You might also want to have
a look at C<ev_set_io_collect_interval ()> to increase the amount of
readiness notifications you get per iteration.

one cannot even remove them from the set) than registered in the set
(especially on SMP systems). Libev tries to counter these spurious
notifications by employing an additional generation counter and comparing
that against the events to filter out spurious ones, recreating the set
when required. Epoll also erroneously rounds down timeouts, but gives you
no way to know when and by how much, so sometimes you have to busy-wait
because epoll returns immediately despite a nonzero timeout. And last
not least, it also refuses to work with some file descriptors which work
perfectly fine with C<select> (files, many character devices...).

Epoll is truly the train wreck among event poll mechanisms, a frankenpoll,

feature-first, correctness-later approach, and is slower than epoll, so
it is not used by default.

One important misdesign is that when sleeping in io_uring, the kernel
wrongly counts that as disk I/O wait, keeping loadavg and a cpu core
"virtually" busy, even if nothing actually waits for disk or uses CPU.

If your application forks frequently, then this backend might be faster,
as setting it up again after a fork is far more efficient with this
backend, and it also doesn't suffer from the epoll design flaw of
receiving events for closed file descriptors.

to spend more time collecting timeouts, at the expense of increased
latency/jitter/inexactness (the watcher callback will be called
later). C<ev_io> watchers will not be affected. Setting this to a non-null
value will not introduce any overhead in libev.

Many (busy) programs can usually benefit by setting the I/O collect
interval to a value near C<0.1> or so, which is often enough for
interactive servers (of course not for games), likewise for timeouts. It
usually doesn't make much sense to set it to a lower value than C<0.01>,
as this approaches the timing granularity of most systems. Note that if
you do transactions with the outside world and you can't increase the

situation, and no known thread-safe method of removing the connection to
cope with overload is known (to me).

One of the easiest ways to handle this situation is to just ignore it
- when the program encounters an overload, it will just loop until the
situation is over. While this is a form of busy waiting, no OS offers an
event-based way to handle this situation, so it's the best one can do.

A better way to handle the situation is to log any errors other than
C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such
messages, and continue as usual, which at least gives the user an idea of

Libev doesn't normally do any kind of I/O itself, and so is not blocking
the process. The exception are C<ev_stat> watchers - those call C<stat
()>, which is a synchronous operation.

For local paths, this usually doesn't matter: unless the system is very
busy or the intervals between stat's are large, a stat call will be fast,
as the path data is usually in memory already (except when starting the
watcher).

For networked file systems, calling C<stat ()> can block an indefinite
time due to network issues, and even under good conditions, a stat call