Skip to content

[BUG] Return early with empty query embeddings (#3181) #631

[BUG] Return early with empty query embeddings (#3181)

[BUG] Return early with empty query embeddings (#3181) #631

Triggered via push November 21, 2024 22:30
Status Failure
Total duration 49m 54s
Billable time 1h 39m
Artifacts 62
check-tag
0s
check-tag
Matrix: Go tests / test
Matrix: python-tests / test-single-node-integration-stress
Matrix: python-tests / test-single-node-integration
Matrix: python-tests / test-stress
Matrix: python-tests / test-thin-client
Matrix: python-tests / test
Matrix: Rust tests / test-benches
Matrix: Rust tests / test-integration
Matrix: Rust tests / test
get-version
17s
get-version
JavaScript client tests  /  test
2m 16s
JavaScript client tests / test
Go tests  /  cluster-test
5m 11s
Go tests / cluster-test
Matrix: python-tests / test-cluster-integration
Deploy docs to Vercel
2m 5s
Deploy docs to Vercel
python-tests  /  merge-cluster-logs
3s
python-tests / merge-cluster-logs
Publish to DockerHub and GHCR
5m 46s
Publish to DockerHub and GHCR
Publish to PyPI
1m 3s
Publish to PyPI
Publish thin client to PyPI
1m 19s
Publish thin client to PyPI
Make GitHub release
0s
Make GitHub release
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Deploy docs to Vercel
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Publish to DockerHub and GHCR
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/login-action@v2.1.0, docker/build-push-action@v3.2.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
built-chromadb-package
32.1 MB
cluster_logs_test_add_3.10
962 KB
cluster_logs_test_add_3.11
625 KB
cluster_logs_test_add_3.12
691 KB
cluster_logs_test_add_3.8
602 KB
cluster_logs_test_add_3.9
770 KB
cluster_logs_test_collection_3.10
37.8 KB
cluster_logs_test_collection_3.11
37.8 KB
cluster_logs_test_collection_3.12
37.7 KB
cluster_logs_test_collection_3.8
37.6 KB
cluster_logs_test_collection_3.9
38 KB
cluster_logs_test_collections_3.10
231 KB
cluster_logs_test_collections_3.11
299 KB
cluster_logs_test_collections_3.12
232 KB
cluster_logs_test_collections_3.8
126 KB
cluster_logs_test_collections_3.9
155 KB
cluster_logs_test_collections_with_database_tenant_3.10
535 KB
cluster_logs_test_collections_with_database_tenant_3.11
583 KB
cluster_logs_test_collections_with_database_tenant_3.12
86.1 KB
cluster_logs_test_collections_with_database_tenant_3.8
627 KB
cluster_logs_test_collections_with_database_tenant_3.9
481 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.10
35.4 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.11
35.5 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.12
35.3 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.8
36 KB
cluster_logs_test_collections_with_database_tenant_overwrite_3.9
35.3 KB
cluster_logs_test_embeddings_3.10
1.04 MB
cluster_logs_test_embeddings_3.11
735 KB
cluster_logs_test_embeddings_3.12
949 KB
cluster_logs_test_embeddings_3.8
914 KB
cluster_logs_test_embeddings_3.9
643 KB
cluster_logs_test_filtering_3.10
411 KB
cluster_logs_test_filtering_3.11
540 KB
cluster_logs_test_filtering_3.12
532 KB
cluster_logs_test_filtering_3.8
363 KB
cluster_logs_test_filtering_3.9
417 KB
cluster_logs_test_logservice_3.10
42.6 KB
cluster_logs_test_logservice_3.11
43.2 KB
cluster_logs_test_logservice_3.12
42.7 KB
cluster_logs_test_logservice_3.8
42.6 KB
cluster_logs_test_logservice_3.9
42.4 KB
cluster_logs_test_memberlist_provider_3.10
37.5 KB
cluster_logs_test_memberlist_provider_3.11
36.6 KB
cluster_logs_test_memberlist_provider_3.12
37.4 KB
cluster_logs_test_memberlist_provider_3.8
36.3 KB
cluster_logs_test_memberlist_provider_3.9
36.8 KB
cluster_logs_test_producer_consumer_3.10
34.5 KB
cluster_logs_test_producer_consumer_3.11
35.2 KB
cluster_logs_test_producer_consumer_3.12
34.9 KB
cluster_logs_test_producer_consumer_3.8
34.9 KB
cluster_logs_test_producer_consumer_3.9
34.9 KB
cluster_logs_test_sanity_3.10
73.3 KB
cluster_logs_test_sanity_3.11
77.7 KB
cluster_logs_test_sanity_3.12
78.3 KB
cluster_logs_test_sanity_3.8
79.3 KB
cluster_logs_test_sanity_3.9
77.8 KB
cluster_logs_test_system_3.10
50.1 KB
cluster_logs_test_system_3.11
50.3 KB
cluster_logs_test_system_3.12
49.8 KB
cluster_logs_test_system_3.8
49.5 KB
cluster_logs_test_system_3.9
49.9 KB
cluster_test_logs
14.8 MB