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]: compilation failed due to CI conflicts #38224

Closed
1 task done
jaime0815 opened this issue Dec 5, 2024 · 0 comments
Closed
1 task done

[Bug]: compilation failed due to CI conflicts #38224

jaime0815 opened this issue Dec 5, 2024 · 0 comments
Assignees
@jaime0815
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

@jaime0815
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

img_v3_02h9_e347144f-cbd1-4f61-808a-3fd074e3071g

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@jaime0815 jaime0815 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 Dec 5, 2024
@jaime0815 jaime0815 assigned yanliang567 and jaime0815 and unassigned yanliang567 Dec 5, 2024
@jaime0815 jaime0815 mentioned this issue Dec 5, 2024
Merged
xiaofan-luan pushed a commit that referenced this issue Dec 5, 2024
@jaime0815
fix: compilation failed due to CI conflicts (#38222)
af288a9 
issue: #38224

Signed-off-by: jaime <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaime0815 jaime0815

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

No branches or pull requests
2 participants
@jaime0815 @yanliang567