Module: Karafka::Errors

Defined in:
lib/karafka/errors.rb

Overview

Namespace used to encapsulate all the internal errors of Karafka

Constant Summary collapse

BaseError =

Base class for all the Karafka internal errors

Class.new(StandardError)
ParserError =

Should be raised when we attemp to parse incoming params but parsing fails

If this error (or its descendant) is detected, we will pass the raw message
into params and proceed further

Class.new(BaseError)
NonMatchingRouteError =

Raised when router receives topic name which does not correspond with any routes This can only happen in a case when:

- you've received a message and we cannot match it with a consumer
- you've changed the routing, so router can no longer associate your topic to
  any consumer
- or in a case when you do a lot of metaprogramming and you change routing/etc on runtime

In case this happens, you will have to create a temporary route that will allow you to “eat” everything from the Sidekiq queue.

See Also:

Class.new(BaseError)
InvalidResponderUsage =

Raised when we don’t use or use responder not in the way it expected to based on the topics usage definitions

Class.new(BaseError)
InvalidResponderMessageOptions =

Raised when options that we provide to the responder to respond aren’t what the schema requires

Class.new(BaseError)
InvalidConfiguration =

Raised when configuration doesn’t match with validation schema

Class.new(BaseError)
MissingBootFile =

Raised when we try to use Karafka CLI commands (except install) without a bootfile

Class.new(BaseError)
MissingClient =

Raised when we want to read a persisted thread messages consumer but it is unavailable This should never happen and if it does, please contact us

Class.new(BaseError)
UnregisteredMonitorEvent =

Raised when want to hook up to an event that is not registered and supported

Class.new(BaseError)
ForcefulShutdown =

Raised when we’ve waited enough for shutting down an unresponding process

Class.new(BaseError)