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]: nil array field will cause panic #33074

Closed
1 task done
sunby opened this issue May 15, 2024 · 1 comment
Closed
1 task done

[Bug]: nil array field will cause panic #33074

sunby opened this issue May 15, 2024 · 1 comment
Assignees
@sunby
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sunby
Copy link
Contributor

sunby commented May 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:v2.3.15
- 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

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xf8 pc=0x446570a]
goroutine 878415 [running]:
panic({0x4be4d20, 0x75b6870})
/usr/local/go/src/runtime/panic.go:987 +0x3bb fp=0xc0022bd308 sp=0xc0022bd248 pc=0x1aebcdb
runtime.panicmem(...)
/usr/local/go/src/runtime/panic.go:260
runtime.sigpanic()
/usr/local/go/src/runtime/signal_unix.go:841 +0x37d fp=0xc0022bd368 sp=0xc0022bd308 pc=0x1b03fdd
github.com/milvus-io/milvus/internal/proxy.(*validateUtil).checkArrayElement(0xc005bf0cd0?, 0x0?, 0x0?)
/go/src/github.com/milvus-io/milvus/internal/proxy/validate_util.go:474 +0x24a fp=0xc0022bd568 sp=0xc0022bd368 pc=0x446570a

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@sunby sunby 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 May 15, 2024
@yanliang567
Copy link
Contributor

/assign @sunby
/unassign

@sre-ci-robot sre-ci-robot assigned sunby and unassigned yanliang567 May 16, 2024
@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 May 16, 2024
This was referenced May 17, 2024
Merged
Merged
sre-ci-robot pushed a commit that referenced this issue May 17, 2024
@sunby
fix: check array field data is nil before getting the type (#33114)
5c6de47 
issue: #33074

Signed-off-by: sunby <sunbingyi1992@gmail.com>
xiaofan-luan pushed a commit that referenced this issue May 18, 2024
@sunby
fix: check array field data is nil before getting the type (#33119)
b073407 
issue: #33074

---------

Signed-off-by: sunby <sunbingyi1992@gmail.com>
@sunby sunby closed this as completed May 20, 2024
sunby added a commit to sunby/milvus that referenced this issue May 23, 2024
@sunby
fix: check array field data is nil before getting the type (milvus-io…
6168523 
…#33114)

issue: milvus-io#33074

Signed-off-by: sunby <sunbingyi1992@gmail.com>
@sunby sunby mentioned this issue May 23, 2024
Merged
czs007 pushed a commit that referenced this issue May 24, 2024
@sunby
fix: check array field data is nil before getting the type (#33114) (#…
e3f1331 
…33311)

issue: #33074
pr: #33114

---------

Signed-off-by: sunby <sunbingyi1992@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sunby sunby

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
@sunby @yanliang567