You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
Would be nice
Please provide a clear description of problem this feature solves
Even when the nv-ingest container is successfully launched, the log shows
nv-ingest-ms-runtime-1 | 2024-10-16 19:37:12,116 - ERROR - Failed to create new connection using: ece0745f72fd43e1ba331491b9b71eb8
nv-ingest-ms-runtime-1 | 2024-10-16 19:37:12,116 - ERROR - Failed to connect to milvus: <MilvusException: (code=2, message=Fail connecting to server on milvus:19530. Timeout)>
Describe the feature, and optionally a solution or implementation and any alternatives
It says ERROR but it is intended behavior (when there is no milvus service running, it is simply logged and the pipeline is built successfully). We should imporve logging so it's not confusing to the user.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
Would be nice
Please provide a clear description of problem this feature solves
Even when the nv-ingest container is successfully launched, the log shows
Describe the feature, and optionally a solution or implementation and any alternatives
It says ERROR but it is intended behavior (when there is no milvus service running, it is simply logged and the pipeline is built successfully). We should imporve logging so it's not confusing to the user.
Additional context
No response
The text was updated successfully, but these errors were encountered: