Pyzeebe

Latest version: v4.1.0

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

Scan your dependencies

Page 3 of 7

3.0.2

Fixes

- Fix bug where decorators that were added to the worker were not propagated to the tasks in included routers - 282
- Fix bug where variables were not given to decorators after the job was performed - 284

3.0.1

Changes

- Raise pyzeebe errors from the underlying grpc error for better stack traces
- Raise `UnkownGrpcStatusCodeError` instead of reraising grpc error when encountering an unexpected status code

Fixes

- Fix bug where workers on python 3.6 would use `event_loop.create_task` which was introduced in python 3.7

3.0.0

Changes

* Support for zeebe 1.x.x
* Naming changed accoridingly (workflow -> process)
* Support async tasks. See [docs](https://pyzeebe.readthedocs.io/en/latest)
* Add ability to provide custom grpc channels
* Add builtin grpc creators (`create_insecure_channel`, `create_secure_channel` and `create_camunda_cloud_channel`)
* Add ability to access job inside a task
* Limit amount of jobs that can run concurrently per task

3.0.0rc5

Changes

* Limit running jobs per task instead of worker - 202
* Add parameter to `task` decorator called `max_running_jobs`
* Removed `max_jobs_to_activate` from worker configuration

Fixes

* Fix issue where wrong audience value would result in `InvalidCamundaCloudCredentialsError` - 217

3.0.0rc4

Changes
- Raise ProcessTimeoutError when a process takes too long to complete using `run_process_with_result`
- Add support for camunda cloud regions - 209

Fixes

- Fix logging when failed to poll for jobs (in `JobPoller`) - 205
- Fix bug where the worker would stop after processing `max_task_count` - 201
- Fix bug where the worker would crash after a job is reactivated - 212
- Fix bug where the worker would not continue after zeebe experiences a restart - 213
- Fix bug where inject job parameter would not contain variables - 207

3.0.0rc3

Changes

- `ZeebeWorker` and `ZeebeClient` now accept a `grpc.aio.Channel` instance in their constructor instead of connection parameters (hostname, port etc.)
- Add three easy ways to create a grpc channel:
- `create_insecure_channel`
- `create_secure_channel`
- `create_camunda_cloud_channel`

New API example:

python
from pyzeebe import ZeebeWorker, ZeebeClient, create_insecure_channel

channel = create_insecure_channel("hostname", 26500)
worker = ZeebeWorker(channel)
client = ZeebeClient(channel)

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.