binbin comments

Results 247 comments of


                                            binbin

[Bug]: [milvus_client][Defer] The error message is not valid when input invalid type data to "db_name" of interface "using_database"

/assign @czs007

[Bug]: [milvus_client][milvus] The error msg does not show the complete usage for query without all the required parameters

/assign @czs007

[Bug]: [milvus_client][milvus] Created HNSW index failed without ef input reporting "efConstruction out of range: [1, 2147483647])>"

And the metric_type did not change yet.

[Bug]: [milvus_client][milvus] Created HNSW index failed without ef input reporting "efConstruction out of range: [1, 2147483647])>"

/assign @czs007

[Bug]: [milvus_client][milvus] Created HNSW index failed without ef input reporting "efConstruction out of range: [1, 2147483647])>"

Not fixed with new error: pymilvus: 2.4.0rc30 milvus: master-20240205-a68b3213 results: ``` >>> index_params = milvus_client.prepare_index_params() >>> index_params.add_index(field_name = "vector", index_type="HNSW", metric_type="L2") >>> >>> milvus_client.create_index(collection_name, index_params) RPC error: [create_index], , Failed...

[Bug]: [milvus_client][milvus] Created HNSW index failed without ef input reporting "efConstruction out of range: [1, 2147483647])>"

It created the index successfully when specify all the index parameters: ``` >>> index_params.add_index(field_name = "vector", index_type="HNSW", metric_type="L2", efConstruction=100, M=10) >>> milvus_client.create_index(collection_name, index_params) >>> >>> milvus_client.describe_index(collection_name, "vector") {'index_type': 'HNSW', 'metric_type':...

[Bug]: [milvus_client][milvus] Created HNSW index failed without ef input reporting "efConstruction out of range: [1, 2147483647])>"

But maybe we could have an enhancement, could we tell user all the required parameter when did not input all the parameters here: ``` >>> index_params = milvus_client.prepare_index_params() >>> index_params.add_index(field_name...

[Bug]: Inserting data raises error `getSegmentID failed: SegmentIDAllocator failRemainRequest unexpected error` when running `test_e2e.py` without any chaos

Same errors when running CI: https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20HA%20CI/detail/PR-24525/8/pipeline/110/ collection name: search_collection_mTv1Ce7E logs: [artifacts-milvus-standalone-PR-24525-8-pymilvus-e2e-logs.tar.gz](https://jenkins.milvus.io:18080/job/Milvus%20HA%20CI/job/PR-24525/8/artifact/artifacts-milvus-standalone-PR-24525-8-pymilvus-e2e-logs.tar.gz) Error: ``` [2023-06-05T04:10:18.258Z] [2023-06-05 04:10:04 - ERROR - pymilvus.decorators]: RPC error: [insert_rows], , (decorators.py:108) [2023-06-05T04:10:18.258Z] [2023-06-05 04:10:04 - ERROR...

[Bug]: Inserting data raises error `getSegmentID failed: SegmentIDAllocator failRemainRequest unexpected error` when running `test_e2e.py` without any chaos

Same error in milvus: master-20230802-df26b909 collection name:test_search_collection_dynamic_1 log: https://grafana-4am.zilliz.cc/explore?orgId=1&left=%7B%22datasource%22:%22Loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bcluster%3D%5C%22devops%5C%22,namespace%3D%5C%22chaos-testing%5C%22,pod%3D~%5C%22master-memory-no-802-hgigo.*%5C%22%7D%22%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D error: ``` RPC error: [insert_rows], , Traceback (most recent call last): File "./23406.py", line 40, in res = collection.insert(rows) File "/usr/local/lib/python3.8/dist-packages/pymilvus/orm/collection.py",...

[Bug]: Search failed with error `reason=Query 23 failed, reason context canceled err` after reinstallation

@congqixia could you please have a look first? Thanks.