Nameko

Latest version: v2.14.1

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 11

1.11.5

Not secure
--------------

Released 2014-11-18

* Have the standalone rpc proxy mark its reply queues as auto-delete, to stop
them staying around after use.

1.11.4

Not secure
--------------

Released 2014-11-10

* Make :class:`~nameko.rpc.RpcConsumer` more robust against failures in the
:class:`~nameko.rpc.Rpc` provider.
* Add a new exception :class:`~nameko.exceptions.MalformedRequest` that RPC
providers can raise if they detect an invalid message. Raise this exception
in the default ``Rpc`` provider if ``args`` or ``kwargs`` keys are missing
from the message.
* Fix issues in queue consumer tests against non-localhost brokers.
* Upgrade to eventlet 0.15.2.
* Include pyrabbit in ``requirements.txt`` (no longer just for tests).
* Catch dying containers in the entrypoint_hook to avoid hangs.
* Add ``expected_exceptions`` kwarg to the rpc entrypoint to enable different
exception handling (in dependencies) for user vs system errors.

1.11.3

Not secure
--------------

Released 2014-10-10

* Add more logging for workers killed by
:meth:`~nameko.containers.ServiceContainer.kill`.

1.11.2

Not secure
--------------

Released 2014-09-18

* Add a default implementation for ``acquire_injection`` (returning ``None``)
for dependency providers that are used for side-effects rather than injecting
dependencies.

1.11.1

Not secure
--------------

Released 2014-09-15

* New test helper :func:`~nameko.testing.services.entrypoint_waiter` to wait
for entrypoints (e.g. event handlers) to complete.

1.11.0

Not secure
--------------

Released 2014-09-01

* Raise a specific ``RpcTimeout`` error in the RPC proxy rather than
``socket.timeout`` to avoid confusing kombu's ``Connection.ensure``
* Improve logging helpers
* Use ``inspect.getcallargs`` instead of shadow lambda for RPC argument
checking
* Add default retry policies to all publishers
* Stricter handling of connections between tests
* Workarounds for RabbitMQ bugs described at
https://groups.google.com/d/topic/rabbitmq-users/lrl0tYd1L38/discussion

Page 7 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.