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]: Repeated Error Code in Milvus segcore and go layer. #37357

Closed
1 task done
chyezh opened this issue Nov 1, 2024 · 3 comments
Closed
1 task done

[Bug]: Repeated Error Code in Milvus segcore and go layer. #37357

chyezh opened this issue Nov 1, 2024 · 3 comments
Assignees
@chyezh
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@chyezh
Copy link
Contributor

chyezh commented Nov 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: be71b981460e70e695d7f1dc28738bca07e7e688
- 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

Go side:

	ErrSegcoreFollyOtherException = newMilvusError("segcore folly other exception", 2200, false) // throw from segcore.
	ErrSegcoreFollyCancel         = newMilvusError("segcore Future was canceled", 2201, false)   // throw from segcore.
	// import
	ErrImportFailed = newMilvusError("importing data failed", 2100, false)

	// Search/Query related
	ErrInconsistentRequery = newMilvusError("inconsistent requery result", 2200, true)

Cpp side:

    OutOfRange = 2037,
    GcpNativeError = 2038,
    KnowhereError = 2100,

    // timeout or cancel related.
    FollyOtherException = 2200,
    FollyCancel = 2201

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@chyezh chyezh 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 1, 2024
@chyezh
Copy link
Contributor Author

chyezh commented Nov 1, 2024

/assign

This was referenced Nov 1, 2024
Merged
Closed
@yanliang567
Copy link
Contributor

/unassign

@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 1, 2024
sre-ci-robot pushed a commit that referenced this issue Nov 5, 2024
@chyezh
fix: repeated error code in milvus and segcore (#37359)
9a0e1c8 
issue: #37357

Signed-off-by: chyezh <[email protected]>
@chyezh chyezh mentioned this issue Nov 5, 2024
Merged
sre-ci-robot pushed a commit that referenced this issue Nov 7, 2024
@chyezh
fix: repeated error code in milvus and segcore (#37449)
cea8c75 
issue: #37357
pr: #37359

Signed-off-by: chyezh <[email protected]>
@chyezh
Copy link
Contributor Author

chyezh commented Nov 7, 2024

should be fixed

@chyezh chyezh closed this as completed Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chyezh chyezh

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
No milestone
Development

No branches or pull requests
2 participants
@chyezh @yanliang567