./devel/ruby-activejob52, Job classes that can be run by a variety of queueing backends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 5.2.4.5, Package name: ruby26-activejob52-5.2.4.5, Maintainer: minskim

Active Job is a framework for declaring jobs and making them run on a
variety of queueing backends. These jobs can be everything from
regularly scheduled clean-ups, to billing charges, to
mailings. Anything that can be chopped up into small units of work and
run in parallel, really.

It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for
running later. That's one of the most common jobs in a modern web
application: Sending emails outside of the request-response cycle, so
the user doesn't have to wait on it.

The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate
runner". We can then have framework features and other gems build on
top of that, without having to worry about API differences between
Delayed Job and Resque. Picking your queuing backend becomes more of
an operational concern, then. And you'll be able to switch between
them without having to rewrite your jobs.

This is for Ruby on Rails 5.2.


Required to run:
[devel/ruby-globalid] [lang/ruby26-base] [devel/ruby-activesupport52]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 64f6e6a89d63288db769481955822b6a6e79a359
RMD160: da5ce55f9c2d8f1bd3f7b4ce742e09d4f1b7e13f
Filesize: 26 KB

Version history: (Expand)


CVS history: (Expand)


   2021-02-11 15:23:42 by Takahiro Kambe | Files touched by this commit (12) | Package updated
Log message:
www/rails52: update to 5.2.4.5

## Rails 5.2.4.5 (February 10, 2021) ##

*   Fix possible DoS vector in PostgreSQL money type

    Carefully crafted input can cause a DoS via the regular expressions used
    for validating the money format in the PostgreSQL adapter.  This patch
    fixes the regexp.

    Thanks to @dee-see from Hackerone for this patch!

    [CVE-2021-22880]

    *Aaron Patterson*
   2020-09-10 16:13:12 by Takahiro Kambe | Files touched by this commit (12) | Package updated
Log message:
www/ruby-rails52: update to  5.2.4.4

Update Ruby on Rails 52 to 5.2.4.4.

Security fix in ruby-actionview52.

## Rails 5.2.4.4 (September 09, 2020) ##

*   [CVE-2020-15169] Fix potential XSS vulnerability in the `translate`/`t` helper

    *Jonathan Hefner*
   2020-05-19 17:35:30 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob52: update to 5.2.4.3

Update ruby-activejob52 to 5.2.4.3.

## Rails 5.2.4.3 (May 18, 2020) ##

*   No changes.
   2020-03-20 16:38:57 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob52: update to 5.2.4.2

Update ruby-activejob52 to 5.2.4.2.

* No change except version.
   2019-04-14 12:31:25 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
devel/ruby-activejob52: update to 5.2.3

## Rails 5.2.3 (March 27, 2019) ##

*   No changes.

## Rails 5.2.2.1 (March 11, 2019) ##

*   No changes.
   2019-03-03 15:47:19 by Takahiro Kambe | Files touched by this commit (4)
Log message:
devel/ruby-activejob52: add version 5.2.2 package

Add ruby-activejob52 version 5.2.2 package.

Active Job is a framework for declaring jobs and making them run on a
variety of queueing backends. These jobs can be everything from
regularly scheduled clean-ups, to billing charges, to
mailings. Anything that can be chopped up into small units of work and
run in parallel, really.

It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for
running later. That's one of the most common jobs in a modern web
application: Sending emails outside of the request-response cycle, so
the user doesn't have to wait on it.

The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate
runner". We can then have framework features and other gems build on
top of that, without having to worry about API differences between
Delayed Job and Resque. Picking your queuing backend becomes more of
an operational concern, then. And you'll be able to switch between
them without having to rewrite your jobs.

This is for Ruby on Rails 5.2.