Heads up This site is currently under heavy development.
Subscribe Get it delivered — the daily firehose, filtered to the tools you run, plus the documentation changes vendors never announce. Compare plans →

The AI Toolchain — issue -432, November 28, 2019

THE AI TOOLCHAIN NO. -432
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED NOVEMBER 28, 2019 · EVERY WEEKDAY
EDITIONS tail grep head diff uniq

The daily firehose — everything the toolchain shipped today, already filtered.

// HOW THIS ISSUE IS MADE

We read every release from the 174 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.

VIEW
ISSUE VIEW full issue
Do you prefer this view?
$ tct list   # 3 tools matched
AI & LLM Tooling
◆  AI Model & Data Infrastructure

NVIDIA Triton Inference Server

Sources Release notes → v1.8.0 NOTES

Triton v1.8.0 adds CUDA shared memory support and string tensor handling in perf_client

└──▷ GET THIS VERSION
$ git clone --branch v1.8.0 https://github.com/triton-inference-server/server.git
# already have the repo? check out this version:
$ git checkout v1.8.0
  • Adds CUDA shared memory support, expanding shared-memory capabilities beyond CPU/pinned memory.
  • Adds string tensor support to perf_client, enabling performance benchmarking of string-typed inputs and outputs.
  • Improves perf_client command-line arguments for easier use while maintaining compatibility with existing arguments.
  • Improves pinned-memory efficiency for ensemble models.
└──▷ BREAKING ON UPGRADE
  • !In the C++ client library, the non-callback version of AsyncRun is removed.
  • !In the C++ client library, GetReadyAsyncRequest is removed.
  • !In the C++ client library, the signature of GetAsyncRunResults is changed — the is_ready and wait arguments are removed.
  • !In the Python client library, the non-callback version of async_run is removed.
  • !In the Python client library, get_ready_async_request is removed.
  • !In the Python client library, the signature of get_async_run_results is changed — the wait argument is removed.
Was this useful?
Other / Uncategorized
◆  VECTOR DB RAG

Milvus

Sources Release notes → v0.5.3 2 RELEASES · 2019-11-04 → 2019-11-13 NOTES STABLE

Milvus v0.5.3 doubles search-result transmission speed and adds new SDK APIs for id/distance retrieval across Python, Java, and C++.

└──▷ GET THIS VERSION
$ git clone --branch v0.5.3 https://github.com/milvus-io/milvus.git
# already have the repo? check out this version:
$ git checkout v0.5.3
└──▷ USE IT
Iterate over large search results efficiently in Python when nq and topk are large, using the new separate id and distance arrays.
python
for id_list, dis_list in zip(results.id_array, results.distance_array):
    for id, dis in zip(id_list, dis_list):
        print("id={}, distance={}".format(id, dis))
Retrieve a specific search result entry by query index and rank using the new indexed accessor in the Python SDK.
python
id = results.id_array[i][j]
distance = results.distance_array[i][j]
  • Adds results.id_array[i][j] and results.distance_array[i][j] accessors in the Python SDK to retrieve a specific target vector's id and distance from search results.
  • Splits search result ids and distances into separate arrays (results.id_array, results.distance_array) in the Python SDK, reducing API response time and enabling faster looping when nq and topk are large.
  • Adds getResultIdsList and getResultDistancesList methods to the Java SDK for retrieving search result ids and distances separately with better performance, alongside the existing getQueryResultsList returning QueryResult objects.
  • Adds keepalive and idleTimeout settings in the Java SDK when connecting to the Milvus server.
  • Doubles the transmission speed of search results to client applications via gRPC message optimizations and API changes.
+2 moreshow less
  • Enhances search performance of IVF_SQ8H index type.
  • C++ SDK now ships as a shared library.
└──▷ BREAKING ON UPGRADE
  • !The gRPC generated-code API has changed in v0.5.3; clients relying on the previous generated API will need to update their code.
1 more release in this issue · 2019-11-04 → 2019-11-13
v0.5.1 NOTES STABLE

Milvus v0.5.1 adds GPU searching threshold control and pure GPU mode for IVFSQ8 and IVFFlat indexes.

└──▷ GET THIS VERSION
$ git clone --branch v0.5.1 https://github.com/milvus-io/milvus.git
# already have the repo? check out this version:
$ git checkout v0.5.1
  • Adds a GPU searching threshold to control the trigger point for GPU execution during vector search.
  • Supports pure GPU mode for IVFSQ8 and IVFFlat index types.
  • Enables CPU-based index building as an option.
Was this useful?

Weaviate

Sources Release notes → 0.21.2 4 RELEASES · 2019-11-06 → 2019-11-28 NOTES STABLE

Weaviate 0.21.2 adds dedicated /v1/.well-known/live and /v1/.well-known/ready health endpoints that bypass auth.

└──▷ GET THIS VERSION
$ git clone --branch 0.21.2 https://github.com/weaviate/weaviate.git
# already have the repo? check out this version:
$ git checkout 0.21.2
└──▷ TRY IT
Use the dedicated liveness endpoint in a Kubernetes liveness probe so auth (e.g. OIDC) never blocks the health check.
$ curl -sf http://weaviate:8080/v1/.well-known/live && echo 'alive'
Use the readiness endpoint in a load-balancer or Kubernetes readiness probe to gate traffic until Weaviate is fully up.
$ curl -sf http://weaviate:8080/v1/.well-known/ready && echo 'ready'
  • Adds unauthenticated liveness endpoint GET /v1/.well-known/live returning 204 No Content when the Weaviate instance is alive, bypassing OIDC and other auth schemes.
  • Adds unauthenticated readiness endpoint GET /v1/.well-known/ready returning 204 No Content when the instance is ready to serve traffic, decoupled from auth-protected endpoints like /v1/meta.
3 more releases in this issue · 2019-11-06 → 2019-11-28
0.21.1 NOTES STABLE

Weaviate 0.21.1 adds wildcard string matching via the Like operator in where filters.

└──▷ GET THIS VERSION
$ git clone --branch 0.21.1 https://github.com/weaviate/weaviate.git
# already have the repo? check out this version:
$ git checkout 0.21.1
  • Adds Like operator to where filters, enabling wildcard partial-match searches on string fields using * glob syntax (e.g. valueString: "Ap*e" matches "Apple" and "Apache").
0.21.0 NOTES STABLE

Weaviate 0.21.0 adds RFC 7396 merge-patch support for PATCH endpoints and reintroduces batch reference adding.

└──▷ GET THIS VERSION
$ git clone --branch 0.21.0 https://github.com/weaviate/weaviate.git
# already have the repo? check out this version:
$ git checkout 0.21.0
└──▷ TRY IT
Partially update a Thing's properties without replacing the whole object — useful for updating a single field in CI/CD pipelines or event-driven workflows.
$ curl -X PATCH 'http://localhost:8080/v1/things/<id>' \
  -H 'Content-Type: application/json' \
  -d '{"class": "Article", "schema": {"title": "Updated Title"}}'
  • Adds RFC 7396 (application/merge-patch+json) merge-style patching to PATCH /v1/things/{id} and PATCH /v1/actions/{id}, replacing the previous RFC 6902 patch semantics; successful merges return 204 No Content.
  • Reintroduces batch-adding of references via POST /v1/batching/references, restoring a capability removed in 0.20.0.
└──▷ BREAKING ON UPGRADE
  • !PATCH /v1/things/ and PATCH /v1/actions/ now use merge-style (RFC 7396) patch semantics instead of RFC 6902 patch semantics; clients sending RFC 6902 JSON Patch bodies will no longer work correctly.
0.20.4 NOTES STABLE

Weaviate 0.20.4 lets you extend the contextionary with custom concepts via a new /v1/c11y/extensions API endpoint.

└──▷ GET THIS VERSION
$ git clone --branch 0.20.4 https://github.com/weaviate/weaviate.git
# already have the repo? check out this version:
$ git checkout 0.20.4
  • Adds a new API (see /v1/c11y/extensions in the swagger spec) to extend the contextionary with custom concepts — overwrite existing concept meanings or add entirely new ones; requires contextionary service version xxxxx-v0.4.0 or later.
  • Introduces the /v1/c11y/concepts/... endpoint family as the replacement for /v1/c11y/words/..., with identical behavior but a cleaner path.
Was this useful?
my-toolchain — 0 tools
paste an install list to detect your tools

A brew list, a Brewfile, requirements.txt, a Dockerfile — or just the product names, free-form. Nothing leaves your browser.

    browse all tools →