Cr8

Latest version: v0.27.2

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

Scan your dependencies

Page 5 of 8

0.14.0

=================

- SSL validation can no be disabled by including ``verify_ssl=False`` in the
hosts URI.

- ``insert-fake-data`` now generates timestamps differently so it works with
``asyncpg``

- JSON output is no longer pretty printed by default. Use ``jq`` or ``python
-mjson.tool`` to do so.

- Release branches can now be used as argument to ``run-crate``. (Something
like ``run-crate 3.1``. This will result in a source checkout and the tarball
will be built locally.)

- Improved the error message when connecting via ``HTTP`` and running into a
``401``.

0.13.0

=================

- Added experimental postgres protocol support. It's available if the optional
``asyncpg`` dependency is installed.

- Bumped the ``aiohttp`` dependency for ``Python 3.7`` support.

- The ``load_data`` directive in spec files now can read ``gzipped`` files.

- Cached local tarballs are now checksummed to avoid re-using a stale tarball
from cache.

- Samples and stdev are now included in the ``runtime_stats`` output if only 1
sample is available.

0.12.1

=================

- ``run-track`` now exists with an error code if any statement failed.

- The statements printed during ``run-spec`` are no longer trimmed.

- Version wildcards like ``2.3.x`` now work correctly for digits greater than
9.

0.12.0

=================

- Fixed an issue that caused ``insert-fake-data`` to fail with a ``TypeError``.

- spec files written in python can now use generators for statements or
arguments.

- Improved the fake data generation for ``insert-fake-data``. It now works for
arrays and objects (although they'll simply be empty)

- Added a ``duration`` option to spec files and ``timeit``

- Added a ``sample-mode`` option to control how many samples will be kept for
the results.

- Improved some error handling and error reporting

0.11.1

=================

- The ``disk.watermark`` settings are no longer set by default by ``run-crate``
in order to be compatible with CrateDB 3.0

- ``run-crate`` will now exit with a failure if process chaining is used and
one of the chained processes failed.

- ``stop()`` on ``CrateNode`` now resets certain attributes correctly, so that
``start()`` doesn't fail with connection errors.

0.11.0

=================

- Added a new default provider for columns of type ``BYTE``.

- Added a new default provider for columns of type ``GEO_SHAPE``, which
provides a POLYGON WKT string.

- Dropped support for Python 3.5

- ``run-crate`` now correctly supports settings using unicode characters.

- ``run-crate`` will now remove old tarballs from the cache folder after a
while.

- ``run-crate`` should now fail faster if an invalid setting is used.

- ``run-crate`` now supports arbitrary command chaining using ``-- cmdname``
If command chaining is used, ``run-crate`` will terminate after all commands
have been run.

- ``run-crate`` should now work correctly if CrateDB is bound to a IPv6 address.

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.