Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: For unsupported tokenizers, the error message is not user-friendly. #37498

Open
1 task done
zhuwenxing opened this issue Nov 7, 2024 · 2 comments
Open
1 task done

[Bug]: For unsupported tokenizers, the error message is not user-friendly. #37498

zhuwenxing opened this issue Nov 7, 2024 · 2 comments
Assignees
@aoiasd
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
2.5.1

Comments

@zhuwenxing
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:master
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

 pymilvus.exceptions.MilvusException: <MilvusException: (code=2000, message=failed to validate text schema, C Runtime Exception: invalid tokenizer parameters
 : segcore error[segcoreCode=2001])>

pointers in the error message, and should be detected on the Go or SDK side, rather than reporting an error to segcore

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@zhuwenxing zhuwenxing added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 7, 2024
@zhuwenxing
Copy link
Contributor Author

/assign @aoiasd

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 7, 2024
@yanliang567 yanliang567 added this to the 2.5.0 milestone Nov 7, 2024
@yanliang567 yanliang567 removed their assignment Nov 7, 2024
@stale Stale
Copy link

stale bot commented Dec 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 8, 2024
@yanliang567 yanliang567 modified the milestones: 2.5.0, 2.5.1 Dec 24, 2024
@stale stale bot removed stale indicates no udpates for 30 days labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aoiasd aoiasd

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
2.5.1
Development

No branches or pull requests
3 participants
@zhuwenxing @aoiasd @yanliang567