Naz

Latest version: v0.8.1

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

Scan your dependencies

Page 4 of 4

0.6.2

- If `naz` were to encounter an SMPP protocol error, it now bails early by unbinding and closing connection: https://github.com/komuw/naz/pull/147

0.6.1

- all the changes in `v0.6.0-beta.1`
- fix a number of logging issues: https://github.com/komuw/naz/pull/105
- cleanly handle termination signals like `SIGTERM`: https://github.com/komuw/naz/pull/106
- validate `naz.Client` arguments: https://github.com/komuw/naz/pull/108
- remove ability to bring your own eventloop: https://github.com/komuw/naz/pull/111
- make `naz` more fault tolerant: https://github.com/komuw/naz/pull/113
- `naz` now has a configurable timeout when trying to connect to SMSC
- `naz` will now be able to detect when the connection to SMSC is disconnected and will attempt to re-connect & re-bind
- bugfix; `asyncio.streams.StreamWriter.drain` should not be called concurrently by multiple coroutines
- when shutting down, `naz` now tries to make sure that write buffers are properly flushed.
- replace naz json config file with a python file: https://github.com/komuw/naz/pull/123
- bugfix: `naz` would attempt to send messages(`submit_sm`) out before it had even connected to SMSC: https://github.com/komuw/naz/pull/124
- added `naz` benchmarks and related fixes that came from the benchmark runs: https://github.com/komuw/naz/pull/127
- when smsc returns `ESME_RMSGQFUL`(message queue is full), `naz` will now call the `throttling` handler.
- fixed a potential memory leak bug in `naz.correlater.SimpleCorrelater`
- added a configurable `connection_timeout` which is the duration that `naz` will wait, for connection related activities with SMSC, before timing out.
- `naz` is now able to re-establish connection and re-bind if the connection between it and SMSC is disconnected.
- renamed `connection_timeout` to `socket_timeout`: https://github.com/komuw/naz/pull/141
- added benchmarks results: https://github.com/komuw/naz/pull/141
- updated documentation and moved it to [komuw.github.io/naz](https://komuw.github.io/naz/); https://github.com/komuw/naz/pull/146

0.6.0beta.1

- Bug fix: https://github.com/komuw/naz/pull/98
the way `naz` was handling correlations was:
- when sending `submit_sm` we save the `sequence_number`
- when we get `submit_sm_resp` we use its `sequence_number` and look it up from Correlater
- when we get a `deliver_sm` request, we use its `sequence_number` and look it up from Correlater

The way `naz` now does it after the fix is;
- when sending `submit_sm` we save the sequence_number
- when we get `submit_sm_resp` we lookup sequence_number and use it for correlation
- Additionally, `submit_sm_resp` has a `message_id` in the body. This is the SMSC message ID of the submitted message.
- We take this `message_id` and save it.
- when we get a `deliver_sm` request, it includes a `receipted_message_id` in the optional body parameters.
- we get that `receipted_message_id` and use it to lookup from where we had saved the one from `submit_sm_resp`
- This release also features an enhancement(and better tests) of correlation: https://github.com/komuw/naz/pull/98

0.5.0beta.1

- Add sphinx documentation: https://github.com/komuw/naz/pull/92
- Start tracking changes in a changelog
- Add more type hints and also run `mypy` across the entire repo: https://github.com/komuw/naz/pull/92
- It's now possible to bring your own logger: https://github.com/komuw/naz/pull/93
- Made the various interfaces in `naz` to inherit from `abc.ABC`: https://github.com/komuw/naz/pull/95
- Fixed a few stylistic issues raised by codacy: https://github.com/komuw/naz/pull/96

Page 4 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.