From: Eric Wong <e@80x24.org>
To: alex0375@gmail.com
Cc: rainbows-public@bogomips.org
Subject: Re: Waiting for deferred actions to finish
Date: Mon, 9 Jan 2017 19:43:37 +0000 [thread overview]
Message-ID: <20170109194337.GA16111@starla> (raw)
In-Reply-To: <CAKwvcL-VH3we4qA1pkNAstTmWvqNA=Rir2N_YiWztV_qbaLQvA@mail.gmail.com>
alex0375@gmail.com wrote:
> Am I missing something? Can this be a part of Rainbows?
Nope, you're not missing anything :)
Rainbows! was missing an EM feature introduced in 2012 :x
I'll make a 5.1.0 release with following patches
(coming in-reply-to this email) soon.
There's also rack 2.x compatibility sitting in rainbows.git.
https://bogomips.org/rainbows-public/20161117033531.GA4454@dcvr/T/
The following changes since commit bd7596e50bd094edf5e5842afb8239c158fe2491:
Revert "t/t0044-autopush.sh: remove test" (2016-12-24 21:42:06 +0000)
are available in the git repository at:
git://bogomips.org/rainbows em-deferred
for you to fetch changes up to f385ed423e11ad40822f688bc592eaa78efa5b34:
eventmachine: wait for deferred actions to finish (2017-01-09 18:59:00 +0000)
----------------------------------------------------------------
Eric Wong (2):
tests: re-enable EventMachine tests, again
eventmachine: wait for deferred actions to finish
SIGNALS | 6 +++---
lib/rainbows/event_machine.rb | 10 +++++++++-
t/GNUmakefile | 2 +-
t/app_deferred.ru | 8 +++++++-
t/t0700-app-deferred.sh | 18 +++++++++++++++---
5 files changed, 35 insertions(+), 9 deletions(-)
next prev parent reply other threads:[~2017-01-09 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 13:43 Waiting for deferred actions to finish alex0375
2017-01-09 19:43 ` Eric Wong [this message]
2017-01-09 19:45 ` [PATCH 1/2] tests: re-enable EventMachine tests, again Eric Wong
2017-01-09 19:45 ` [PATCH 2/2] eventmachine: wait for deferred actions to finish Eric Wong
2017-01-10 7:31 ` Waiting " alex0375
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/rainbows/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170109194337.GA16111@starla \
--to=e@80x24.org \
--cc=alex0375@gmail.com \
--cc=rainbows-public@bogomips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/rainbows.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).