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.

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

[Bug]: wrong semantics in assertion #39346

Open
1 task done
SpadeA-Tang opened this issue Jan 16, 2025 · 2 comments · May be fixed by #39347
Open
1 task done

[Bug]: wrong semantics in assertion #39346

SpadeA-Tang opened this issue Jan 16, 2025 · 2 comments · May be fixed by #39347
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@SpadeA-Tang
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

Image
It should mean to be equal "==", rather than assignment "=".

Expected Behavior

No response

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

@SpadeA-Tang SpadeA-Tang 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 Jan 16, 2025
@chasingegg
Copy link
Contributor

Thanks! It could be removed, same as the above line.

@SpadeA-Tang
Copy link
Contributor Author

/unassign yanliang567

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants