Sneakers now requires Ruby 2.5 or later.
Similar to already supported content type.
Contributed by @ansoncat.
GitHub issue: #449
This releases includes bug fixes, support for more queue-binding options, better management of the Bunny dependency, and improved documentation. Following is a list of the notable changes:
Fixes a bug that would cause Sneakers workers to freeze if an exception
descending from ScriptError
, such as NotImplementedError
, is raised
Contributed by @sharshenov
GitHub Pull Request: 373
The dependency on Bunny is now pinned to the minor version instead of patch, allowing users to benefit from non-breaking updates to Bunny without having to wait for a Sneakers release.
Contributed by @olivierlacan
GitHub Pull Request: #372
It is now possible to set arguments on a queue when connecting to a headers exchange
Contributed by @nerikj
GitHub Pull Request: #358
This release also contains contributions from @ivan-kolmychek (bumping up Bunny dependency), @michaelklishin (improving code style), and @darren987469 (adding examples to the README)
This release contains minor breaking API changes.
This is a breaking change for Sneakers::Worker
implementations.
Timeouts can be disruptive and dangerous depending on what the workers do but not having them can also lead to operational headaches.
The outcome of a lengthy discussion on possible alternatives to the timeout mechanisms is that only applications can know where it is safe to enforce a timeout (and how).
Sneakers::Worker
implementations are now expected to enforce timeouts
in a way that makes sense (and is safe) to them.
GitHub issues: #343.
This release requires Ruby 2.2 and has breaking API changes around custom error handlers.
It is now possible to use a custom connection instance in worker groups.
Contributed by @pomnikita.
GitHub issue: #322
Contributed by Jason Lombardozzi.
GitHub issue: #307
Sneakers now requires Ruby 2.2.
Bunny was upgraded to 2.9.x.
Server Engine dependency was upgraded to 2.0.5.
Contributed by Christoph Wagner.
GitHub issue: #325
Contributed by @adamors.
GitHub issue: #324
To avoid potentially leaking credentials in the log.
Contributed by Kimmo Lehto.
GitHub issue: #301.
Contributed by Andrew Babichev
GitHub issue: #346