Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Set blacklisted exceptions #12

Open
wants to merge 7 commits into
base: skroutz
Choose a base branch
from
Open

Set blacklisted exceptions #12

wants to merge 7 commits into from

Commits on Aug 5, 2019

  1. Introduce BlacklistExceptionsRegistrar module 

    This commit introduces a new module for accessing a class variable
named `blacklist`. This class variable represents exceptions that
will not be pushed to the failed queue when a job fails with an
exception that is included in the blacklist.
Every class that includes this module can access/manipulate its
`blacklist` class variable.
Also it adds a method called `blacklisted_exception_raised?` which
checks if the raised exception belongs to the backend's blacklisted
exceptions.
    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    be5d6ed View commit details
    Browse the repository at this point in the history

  2. Failure::Base: Include the BlacklistExceptionsRegistrar module 

    This commit allows Resque::Failure::Base to include the module
BlacklistExceptionsRegistrar and by extension allowing every
descendant of base class to manipulate its `blacklist` class
variable.
    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    35ca212 View commit details
    Browse the repository at this point in the history

  3. Failure::Redis: Use blacklisted exceptions on save 

    This commit uses the `blacklisted_exception_raised?`, provided
by the BlacklistExceptionsRegistrar module, to determine
if the raised exception of the failed job is a blacklisted
exception and by extension if the job should be pushed to
the failed queue or not.
    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    1fb9dfc View commit details
    Browse the repository at this point in the history

  4. Failure::RedisMultiQueue: Use blacklisted exceptions on save 

    This commit uses the `blacklisted_exception_raised?`, provided
by the BlacklistExceptionsRegistrar module, to determine
if the raised exception of the failed job is a blacklisted
exception and by extension if the job should be pushed to
the failed queue or not.
    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    3366d76 View commit details
    Browse the repository at this point in the history

  5. Failure::Multiple: Use blacklisted exceptions on save 

    This commit uses the `blacklisted_exception_raised?`, provided
by the BlacklistExceptionsRegistrar module, to determine
if the save method of a respective backend should be called
or not if a failed job with a given exception occurs.
    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    ad33827 View commit details
    Browse the repository at this point in the history

  6. Travis: Modify ruby versions

    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    d3d7b80 View commit details
    Browse the repository at this point in the history

  7. Bump version to 1.27.4.skroutz.2

    @konstantinoskostis
    konstantinoskostis committed Aug 5, 2019
    Configuration menu
    Copy the full SHA
    4ff4dad View commit details
    Browse the repository at this point in the history