Jaws-libp

Latest version: v4.8.3

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

Scan your dependencies

Page 2 of 6

4.6.2

- Package JSON data (topics and schema links)

**Full Changelog**: https://github.com/JeffersonLab/jaws-libp/compare/v4.6.1...v4.6.2

4.6.1

- Set Git UNIX execute bit for docker-entrypoint.sh

**Full Changelog**: https://github.com/JeffersonLab/jaws-libp/compare/v4.6.0...v4.6.1

4.6.0

- Use pyproject.toml and drop setup.cfg
- Bump Confluent Kafka lib to 2.2.0
- Use built-in schema references support
- Consolidated admin scripts into this lib (formerly in jaws_scripts package)
- Added Docker support

**Full Changelog**: https://github.com/JeffersonLab/jaws-libp/compare/v4.5.0...v4.6.0

4.5.0

- Added "device" field (https://github.com/JeffersonLab/jaws/issues/36)

4.4.1

- `alarm-registrations` topic name erroneously changed in [EffectiveRegistrationConsumer](https://github.com/JeffersonLab/jaws-libp/commit/855932a0963d8928c5f8b7267a26ee97d25fe5ac)

4.4.0

- AlarmPriority is no longer a Schema Reference (https://github.com/JeffersonLab/jaws/issues/40)
- latching renamed latchable (https://github.com/JeffersonLab/jaws-libp/issues/7)
- effective-activations renamed effective-notifications (https://github.com/JeffersonLab/jaws-libp/issues/4)
- OverriddenAlarmKey renamed AlarmOverrideKey (https://github.com/JeffersonLab/jaws-libp/issues/1)
- enable.auto.commit now is False by default (https://github.com/JeffersonLab/jaws/issues/43)
- Added new AlarmActivationUnion union member NoAlarmActivation (https://github.com/JeffersonLab/jaws/issues/43)
- Console client code now separated into own console client classes to simplify regular client API (https://github.com/JeffersonLab/jaws-libp/issues/8)
- Client API simplified to closer match Java API (jaws-libj) - no longer a separate CacheListener interface
- Removed `NO_ALARM` from AlarmActivationUnion union member EPICSActivation sevr field (https://github.com/JeffersonLab/jaws-libp/issues/5)
- AlarmInstance `producer` field renamed `source` to avoid naming conflicts with Kafka Producer
- AlarmInstance `class` field renamed `alarmclass` to avoid naming conflicts with reserved word in Java and Python
- AlarmActivationUnion and AlarmOverrideUnion `msg` field renamed `union` for clarity
- AlarmActivationUnion union members renamed with `Activation` suffix to match the AlarmOverrideUnion union member `Override` suffix

Page 2 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.