questdb 2.0.2__tar.gz → 2.0.3__tar.gz

{questdb-2.0.2 → questdb-2.0.3}/CHANGELOG.rst

@@ -3,10 +3,22 @@
 Changelog
 =========
 
+2.0.3 (2024-06-06)
+------------------
+
+Patch release with bug fixes. No breaking changes.
+
+Bug fixes
+~~~~~~~~~
+* HTTP timeout wasn't always being correctly applied in the downstream ``c-questdb-client`` dependency.
+* ``request_timeout > 0`` will now be enforced. This was always required, but would not error.
+* Fixed the source distribution "sdist" package: This allows the package to be installed from source
+  via "pip install" on previously unsupported platforms (YMMV).
+
 2.0.2 (2024-04-11)
 ------------------
 
-Patch release with performance bug fix. No breaking changes.
+Patch release with a performance bug fix. No breaking changes.
 
 Bug fixes
 ~~~~~~~~~

{questdb-2.0.2 → questdb-2.0.3}/DEV_NOTES.rst

@@ -108,6 +108,23 @@ As this is very time-consuming, instead download all targets
 (except for Apple Silicon) from the CI.
 
 
+The "sdist" source distribution
+-------------------------------
+
+This is a tarball containing all the sources necessary to build the package
+locally.
+
+Its contents are controlled by the ``MANIFEST.in`` file.
+
+To test it:
+
+.. code-block:: bash
+
+    ./proj clean
+    ./proj sdist
+    python3 -m pip install dist/*.tar.gz --user -v
+
+
 Checking `pip install` works
 ----------------------------
 

{questdb-2.0.2 → questdb-2.0.3}/MANIFEST.in

@@ -9,6 +9,13 @@ include proj
 recursive-include src *.html
 recursive-include src *.pxd
 recursive-include src *.pyx
+recursive-include src *.h
+recursive-include src *.inc
+recursive-include src *.py
+recursive-include src *.md
+recursive-include src *.pxi
+recursive-include src *.c
+graft pystr-to-utf8
 graft c-questdb-client
 prune c-questdb-client/src/tests/json_tests.rs
 prune c-questdb-client/.git

{questdb-2.0.2 → questdb-2.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: questdb
-Version: 2.0.2
+Version: 2.0.3
 Summary: QuestDB client library for Python
 Author-email: Adam Cimarosti <adam@questdb.io>
 License: Apache License 2.0
@@ -56,7 +56,7 @@ and full-connection encryption with
 Quickstart
 ==========
 
-The latest version of the library is 2.0.2 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
+The latest version of the library is 2.0.3 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
 
 ::
 

{questdb-2.0.2 → questdb-2.0.3}/README.rst

@@ -18,7 +18,7 @@ and full-connection encryption with
 Quickstart
 ==========
 
-The latest version of the library is 2.0.2 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
+The latest version of the library is 2.0.3 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
 
 ::
 

{questdb-2.0.2 → questdb-2.0.3}/RELEASING.rst

@@ -61,7 +61,6 @@ From a MacOS ARM computer install UTM.
 
 * Download from https://mac.getutm.app/
 * Install MacOS X 12.4 (Monterey). See https://docs.getutm.app/guest-support/macos/
-* Install Xcode from the App Store
 * Install Rust from https://rustup.rs/
 * Install Firefox
 * Install *all* OFFICIAL Python Releases from Python 3.8 onwards. Use the latest patch version for each minor release. 

{questdb-2.0.2 → questdb-2.0.3}/c-questdb-client/.bumpversion.cfg

@@ -1,6 +1,6 @@
 [bumpversion]
-current_version = 4.0.0
-commit = True
+current_version = 4.0.2
+commit = False
 tag = False
 
 [bumpversion:file:CMakeLists.txt]
@@ -15,10 +15,6 @@ replace = questdb-rs/{new_version}/
 search = version = "{current_version}"
 replace = version = "{new_version}"
 
-[bumpversion:file:questdb-rs/README.md]
-search = questdb-rs = "{current_version}"
-replace = questdb-rs = "{new_version}"
-
 [bumpversion:file:./questdb-rs/README.md]
 search = questdb-rs/{current_version}/
 replace = questdb-rs/{new_version}/

{questdb-2.0.2 → questdb-2.0.3}/c-questdb-client/CMakeLists.txt

@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.15.0)
-project(c-questdb-client VERSION 4.0.0)
+project(c-questdb-client VERSION 4.0.2)
 
 set(CPACK_PROJECT_NAME ${PROJECT_NAME})
 set(CPACK_PROJECT_VERSION ${PROJECT_VERSION})

{questdb-2.0.2 → questdb-2.0.3}/c-questdb-client/README.md

@@ -4,7 +4,7 @@
 This library makes it easy to insert data into [QuestDB](https://questdb.io/).
 
 This client library implements the [InfluxDB Line Protocol](
-https://questdb.io/docs/reference/api/ilp/overview/) (ILP) over TCP or HTTP.
+https://questdb.io/docs/reference/api/ilp/overview/) (ILP) over HTTP and TCP.
 
 * Implementation is in Rust, with no additional
   [run-time or link-time dependencies](doc/BUILD.md#pre-requisites-and-dependencies)
@@ -24,7 +24,7 @@ streaming use cases).
 | Protocol | Record Insertion Reporting | Data Insertion Performance |
 | -------- | -------------------------- | -------------------------- |
 | **[ILP/HTTP](https://questdb.io/docs/reference/api/ilp/overview/)** | Transaction-level (on flush) | **Excellent** |
-| [ILP/TCP](https://questdb.io/docs/reference/api/ilp/overview/)| Errors in logs; Disconnect on error | **Best** (tolerates higher latency networks) |
+| [ILP/TCP](https://questdb.io/docs/reference/api/ilp/overview/)| Errors in logs; Disconnect on error | **Best** (tolerates higher-latency networks) |
 | [CSV Upload via HTTP](https://questdb.io/docs/reference/api/rest/#imp---import-data) | Configurable | Very Good |
 | [PostgreSQL](https://questdb.io/docs/reference/api/postgres/) | Transaction-level | Good |
 
@@ -33,7 +33,7 @@ See the [flush troubleshooting](doc/CONSIDERATIONS.md) docs for more details on
 how to debug ILP/TCP.
 
 For an overview and code examples, see the
-[ILP page of the developer docs](https://questdb.io/docs/develop/insert-data/#influxdb-line-protocol).
+[InfluxDB Line Protocol page of the developer docs](https://questdb.io/docs/develop/insert-data/#influxdb-line-protocol).
 
 To understand the protocol in more depth, consult the
 [protocol reference docs](https://questdb.io/docs/reference/api/ilp/overview/).

{questdb-2.0.2 → questdb-2.0.3}/c-questdb-client/doc/DEPENDENCY.md

@@ -43,7 +43,8 @@ In all examples below, we will attempt to compile:
 
 int main()
 {
-    questdb::ingress::line_sender sender{"localhost", 9009};
+    auto sender = questdb::ingress::line_sender::from_conf(
+        "http::addr=localhost:9000;");
     return 0;
 }
 ```

questdb-2.0.3/c-questdb-client/doc/RELEASING.md

@@ -0,0 +1,90 @@
+# How to publish a new release
+
+## 1. Ensure you're fully in sync with the remote repo
+
+```bash
+git switch main
+git pull
+git status
+```
+
+## 2. Create the release branch
+
+```bash
+git switch -c vX.Y.Z
+```
+
+## 3. Update all the occurrences of the version in the repo
+
+```bash
+bump2version --config-file .bumpversion.cfg <increment>
+```
+
+The `increment` parameter can be:
+
+- `patch`
+- `minor`
+- `major`
+
+Use the one appropriate to the version increment you're releasing.
+
+## 4. Refresh `Cargo.lock`
+
+```bash
+cd questdb-rs-ffi
+cargo clean
+cargo build
+```
+
+## 5. Merge the release branch to master
+
+```bash
+git commit -a -m "Bump version: <current> → <new>"
+git push
+```
+
+Replace the `<current>` and `<new>` placeholders!
+
+Create and merge a PR with the same name: "Bump version: \<current\> → \<new\>"
+
+## 6. Tag the new version
+
+Once the PR is merged, pull main and add the version tag:
+
+```bash
+git switch main
+git pull --prune
+git tag X.Y.Z
+git push --tags
+```
+
+## 7. Create a new release on GitHub
+
+[GitHub Release Page](https://github.com/questdb/c-questdb-client/releases)
+
+On that page you'll see all the previous releases. Follow their manually-written
+style, and note that the style differs between patch, minor, and major releases.
+
+## 8. Publish the Rust crate to crates.io
+
+Ensure once more you're fully in sync with the remote repo:
+
+```bash
+git switch main
+git pull
+git status
+```
+
+Publish the crate:
+
+```bash
+cd questdb-rs
+cargo publish --dry-run --token [your API token from crates.io]
+cargo publish --token [your API token from crates.io]
+```
+
+## 9. Ensure the docs are online on docs.rs
+
+The release is immediately visible on crates.io, but there's a delay until it
+becomes available on [https://docs.rs/](docs.rs). Watch that site and ensure it
+appears there.

{questdb-2.0.2 → questdb-2.0.3}/c-questdb-client/doc/SECURITY.md

@@ -35,7 +35,7 @@ A few important technical details on TLS:
     are managed centrally.
 
 For API usage:
-* Rust: `SenderBuilder`'s [`auth`](https://docs.rs/questdb-rs/4.0.0/questdb/ingress/struct.SenderBuilder.html#method.auth)
-  and [`tls`](https://docs.rs/questdb-rs/4.0.0/questdb/ingress/struct.SenderBuilder.html#method.tls) methods.
+* Rust: `SenderBuilder`'s [`auth`](https://docs.rs/questdb-rs/4.0.2/questdb/ingress/struct.SenderBuilder.html#method.auth)
+  and [`tls`](https://docs.rs/questdb-rs/4.0.2/questdb/ingress/struct.SenderBuilder.html#method.tls) methods.
 * C: [examples/line_sender_c_example_auth.c](../examples/line_sender_c_example_auth.c)
 * C++: [examples/line_sender_cpp_example_auth.cpp](../examples/line_sender_cpp_example_auth.cpp)